Develop Bugs

White Screen

This just started to happen today....every time my screen timeouts...it goes completely blank...i can still hear things and receive calls...but it will stay white for like 20 seconds and then come back on... i am using Ricky's Wm6.1 any help would be great...thanks

zdub27 said:
This just started to happen today....every time my screen timeouts...it goes completely blank...i can still hear things and receive calls...but it will stay white for like 20 seconds and then come back on... i am using Ricky's Wm6.1 any help would be great...thanks
Click to expand...
Click to collapse
Hard-reset if this doesn`t solve it re-flash...

stylez said:
Hard-reset if this doesn`t solve it re-flash...
Click to expand...
Click to collapse
Interesting.... I just started having this problem as well. I went hard reset... not solved. I re-flashed (using proper procedure)... and it was solved for a couple of days... and then returned.
I then used the forum search function, crazy how that works and found this thread.
Hope that helps.

Are you using maniac's AutoKeylock ?
I have experienced this issue ever since loading Rose ROMs - didn't happen on earlier ones.
However, this last time I flashed to the latest update, I did not install AutoKeylock immediately after flashing. I left this off as I had noticed that the screen was going white 30 seconds into calls (which was the timeout I had configured in AutoKeylock) and I wondered if there was a correlation.
Can anyone else who has seen the issue comment on whether they use AutoKeylock or not. It is possible there is some change in the ROM that AutoKeylock does not handle well.
Thanks.

LiverpoolFCfan said:
I have experienced this issue ever since loading Rose ROMs - didn't happen on earlier ones.
However, this last time I flashed to the latest update, I did not install AutoKeylock immediately after flashing. I left this off as I had noticed that the screen was going white 30 seconds into calls (which was the timeout I had configured in AutoKeylock) and I wondered if there was a correlation.
Can anyone else who has seen the issue comment on whether they use AutoKeylock or not. It is possible there is some change in the ROM that AutoKeylock does not handle well.
Thanks.
Click to expand...
Click to collapse
I think that the WSOA (white screen of annoyance) is tied to the low-light function and joggr bar. Go to joggr settings, and be sure that the checkbox with the lowlight function is disabled.

I had the white screen issue for a few days, tried everything.....as soon as I uninstalled GlyphCache 65535 found here, the problem went away

Capper5016 said:
I had the white screen issue for a few days, tried everything.....as soon as I uninstalled GlyphCache 65535 found here, the problem went away
Click to expand...
Click to collapse
it comes and goes its just something messed up that happenes probably nothing to worry about, just little anoying is all.

Check power management registry settings
Hi,
I had this problem once and fixed it by changing the registry settings that control what happens when the device enters various power states. Search the forum about this as the answer is in there somewhere Hope this helps.

Is there a freeware to turn off/on phone radio on schedule?

say if I want to turn off phone radio from 9PM to 8AM, but keep Dash on to use as a PDA. .. Thanks.

qaplus said:
say if I want to turn off phone radio from 9PM to 8AM, but keep Dash on to use as a PDA. .. Thanks.
Click to expand...
Click to collapse
Write a Mortscript to do it.

ehh, that's a bit too difficultf or me..

I think Don'tForget will do what you are wanting.
You can get it from http://dashapps.googlepages.com

Thanks. I tried Don't Forget. But it crashed when it tries to switch to Flight mode.

qaplus said:
ehh, that's a bit too difficultf or me..
Click to expand...
Click to collapse
I will write you up one this weekend and post it here for you.
What times do you want it to switch the radio off and what time to turn it back on?

Bupahs said:
I will write you up one this weekend and post it here for you.
What times do you want it to switch the radio off and what time to turn it back on?
Click to expand...
Click to collapse
Bupahs, that's so nice of you. Can you set it to from 9PM to 8AM? It's just a text script, right? So I can modify it later? Thanks!

I think this should fit the bill nicely http://handheld.softpedia.com/get/System-Utilities/Communications/SleepWell-32308.shtml

There's a pair of programs i use(d). Both by the same company. One will schedule automated events (alarms, shut-off, etc) and the other will record macros.
Essentially you record a macro (choose start at home screen) and work your way into comm manager as if you normally would, and this device will remmeber what you did.
Next you would set an autorun in the second program.
A few things i have noticed..
Doesn't function perfectly when starting in LOCK mode, so you have to fake an unlock by pressing the unlock key and Z, then just press the HANGUP button to make sure it is on the home screen
You have to leave time considering for LAG with your phone, i would give it a good couple of seconds more than it actually takes for each step to make sure it doesnt mess anything up....realize that it isnt remembering your destination, just your keypresses and pauses...
Program has a VERY AKWARD and barely legible font, so trust it!
The auto-run program comes packed with a bunch of automatically programmed alarms and events, so delete them when you install
The names of these programs are:
MacroRecorder and AutoFlight ...both are by CyberHorse i believe

qaplus said:
Bupahs, that's so nice of you. Can you set it to from 9PM to 8AM? It's just a text script, right? So I can modify it later? Thanks!
Click to expand...
Click to collapse
pretty much, I will comment the parts you can edit.
I write so many Mortscripts its pretty simple anymore.

Cyclonezephyrxz7 said:
There's a pair of programs i use(d). Both by the same company. One will schedule automated events (alarms, shut-off, etc) and the other will record macros.
Essentially you record a macro (choose start at home screen) and work your way into comm manager as if you normally would, and this device will remmeber what you did.
Next you would set an autorun in the second program.
A few things i have noticed..
Doesn't function perfectly when starting in LOCK mode, so you have to fake an unlock by pressing the unlock key and Z, then just press the HANGUP button to make sure it is on the home screen
You have to leave time considering for LAG with your phone, i would give it a good couple of seconds more than it actually takes for each step to make sure it doesnt mess anything up....realize that it isnt remembering your destination, just your keypresses and pauses...
Program has a VERY AKWARD and barely legible font, so trust it!
The auto-run program comes packed with a bunch of automatically programmed alarms and events, so delete them when you install
The names of these programs are:
MacroRecorder and AutoFlight ...both are by CyberHorse i believe
Click to expand...
Click to collapse
Personally I like a good simple and small foot print Mortscript. Why install two programs to do what a 5k script will do?

Evi1d33d said:
I think this should fit the bill nicely http://handheld.softpedia.com/get/System-Utilities/Communications/SleepWell-32308.shtml
Click to expand...
Click to collapse
Thanks Evi1d33d. This one works great. The only minor problem is the Edit dialog doesn't like my font. Most messages are truncated.

Off topic but does anyone know a free app that let you schedule when the phone turns on/off?
I think it's almost impossible since the phone isn't running anything when it's off.

Evi1d33d said:
Off topic but does anyone know a free app that let you schedule when the phone turns on/off?
I think it's almost impossible since the phone isn't running anything when it's off.
Click to expand...
Click to collapse
lol, Mortscripts once again. My phone powers on, downloads my mail, feeds, weather, etc then if its the weekend powers off again until I need it if it is the weekday it sets off the alarm to wake me up.

Evi1d33d said:
I think this should fit the bill nicely http://handheld.softpedia.com/get/System-Utilities/Communications/SleepWell-32308.shtml
Click to expand...
Click to collapse
Sleepwell is great, however, I guess I'm missing something....
I can define the hour to turn on airplane mode... how about turn OFF airplane mode? How this software knows when I want my phone back? I couldn't find any settings to it, or am I missing something
I think I got the picture... you define one setting to turn off, and then define another setting to turn on. Is it? Am I right?
Regards.

joeskull said:
Sleepwell is great, however, I guess I'm missing something....
I can define the hour to turn on airplane mode... how about turn OFF airplane mode? How this software knows when I want my phone back? I couldn't find any settings to it, or am I missing something
I think I got the picture... you define one setting to turn off, and then define another setting to turn on. Is it? Am I right?
Regards.
Click to expand...
Click to collapse
There are three options in the app: Flight mode on, Flight mode off and Turn the phone off.

Hi Bupahs any update on the script? thanks

Z-man said:
Hi Bupahs any update on the script? thanks
Click to expand...
Click to collapse
Oh man, I must hang my head in shame on this one, I completely forgot about it
I will post one tomorrow (sunday 8) sorry about that guys.

Ok, I have a couple scripts ready to go.. almost, I need to know for which version of WM to make them, just so there are not errors or unexpected issues.

Bupahs said:
Ok, I have a couple scripts ready to go.. almost, I need to know for which version of WM to make them, just so there are not errors or unexpected issues.
Click to expand...
Click to collapse
i have wm6.1 kavana rom 90123 not 80408 WWE

[TESTING]LCD panel improvements

Hey ho fellas ,
I was working on adding power management + initialisation/de-initialisation sequence for rhodium´s lcd panel. Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
I would like that all of you users that are willing to help to test the kernel ( zImage+modules + latest commits included ) and give some feedback.
Test the power on/off sequence, leave it sleeping for ~30mins and unlock it,...then give me here some feedback on your lcd panel behaviour.
zImage + modules ( mediafire or attachment ):
http://www.mediafire.com/?ny18wpc3z8utxrf
Prerequisites:
- Backup your data.img if you have some valuable data on it ( anyway it should not affect it )
- Delete pm_sleep cmd from your startup.txt

What do you mean by this?
Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
Click to expand...
Click to collapse
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test

Lennyz1988 said:
What do you mean by this?
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test
Click to expand...
Click to collapse
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.

lilchicano said:
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.
Click to expand...
Click to collapse
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life

Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!

uub11 said:
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life
Click to expand...
Click to collapse
Yeah, its a little bit hard to explain, but its like you said.
arrrghhh said:
Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!
Click to expand...
Click to collapse
Yeah, test it out and post your feedback

ReWind402 said:
Yeah, its a little bit hard to explain, but its like you said.
Yeah, test it out and post your feedback
Click to expand...
Click to collapse
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.

uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
I uploaded it here on xda, check the 1st post.

uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
Ha, responded a little late. I removed it...

Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now

Lennyz1988 said:
Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now
Click to expand...
Click to collapse
It would better that pm_sleep has the default value.

Will give this a try as I go about my day today. I don't OC and use pm_sleep=1 yet still get terrible battery life (b/c I'm a power-user, on e-mail constantly). Any positive change will be wonderful We'll see how it goes.

My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...

Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010

Lennyz1988 said:
My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...
Click to expand...
Click to collapse
1. Try deleting pm_sleep from your startup.txt ( then the default value will be used - i recommend that ) or put 1
2. never seen that on android
Anyway i am really sry for the inconvenience regarding launcer pro, kernel change should not affect those kind of settings :s
solevi said:
Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010
Click to expand...
Click to collapse
Yeah its a common problem for now we are investigating this.
So i have a confirmation that the screen is really powered off?
Anyway guys try putting 1 into pm_sleep or deleting it from startup.txt (i recommend the 2nd choice ).

I ran into an interesting problem however I did not see the previous post...
Several time it went into standby (I assume) and the screen was pitch black meaning the backlight was not on. To get it out of standby, I woul click the end button like normal. after a couple of hours I pulled the phone out of my holdster, and it was abnormally hot. I do not have an overclock and my pm sleep is set to 1. I did not press the screen to see if it would respond so maybe that is what was being mentioned in the last post. None of the buttons would bring it back to life and the LED was amber and solid, where typically it would flash with this new zimage and modules. I will try to get it back to that state and see if I can click the screen even though it is dark. One thing that worries me is the battery though. Could this be damaging to it? Even when I did have it overclocked it never reached that temperature.
Anything else I can do to help troubleshoot?
EDIT: Sorry, forgot to mention I am on a Sprint RHOD400

I'm on the RHOD400 model, no OC, pm_sleep=1
Couldn't really get it to be stable, had to switch back to WinMo for the day (and trust me, that's desperation ). Once restarted in my pocket without any interaction on my part. I would press the end key to turn on screen, and had it auto reboot at that point as well. Also got a "sleep of death" twice and had to restart. While in your kernel I didn't have notification LEDs as well (not even for power events), vs the guy above that had blinking red.
I'm sure you'll get it eventually, keep up the hard work!

Hi!
Any news? Are we gonna wait for new kernel with committed code or it development is stalled?

[Q] wakeup screen timeout

hi, considering all the amazing work going on here by the devs, this is really minor.
using Clemsyn froyo 2.2 with Haret but maybe typical question.
when it wakes from sleep with power button the screen stays alight for about 2secs. sometimes it will black out before the white/multicoloured screen goes.
can i change to say 1 min this anywhere like the screen timeout. i always have it set to 10mins for the main display. its no prob to just press end or power to relock.
ps. did have some probs with sound but solved after changing radio from 1.64.08.21,
tried 1.71.09.01 and 1.65.21.18 but no good either. using 1.65.24.36 on kaiser now and seems to be ok.
what is strange about sound is how LOUD everything is compared to the barely audible winmo and whispering ringtones

gazzacbr said:
hi, considering all the amazing work going on here by the devs, this is really minor.
using Clemsyn froyo 2.2 with Haret but maybe typical question.
when it wakes from sleep with power button the screen stays alight for about 2secs. sometimes it will black out before the white/multicoloured screen goes.
can i change to say 1 min this anywhere like the screen timeout. i always have it set to 10mins for the main display. its no prob to just press end or power to relock.
ps. did have some probs with sound but solved after changing radio from 1.64.08.21,
tried 1.71.09.01 and 1.65.21.18 but no good either. using 1.65.24.36 on kaiser now and seems to be ok.
what is strange about sound is how LOUD everything is compared to the barely audible winmo and whispering ringtones
Click to expand...
Click to collapse
The timeout is related to the number of fake v-syncs the phone is doing. There is a parameter to adjust that. Run a search for it as I forget where/how to adjust it.

aceoyame said:
The timeout is related to the number of fake v-syncs the phone is doing. There is a parameter to adjust that. Run a search for it as I forget where/how to adjust it.
Click to expand...
Click to collapse
hmm, ok thanks. will have to do some reading then.
a google search came up with some stuff to check...
and a youtube video:
"Britney Spears : Lip-Sync + Boobs being Fake"
so maybe check that one out also sometime :-D

lmao I wouldn't use google for this search. I would search inside the kaiser forums only. I am pretty sure no other phones have a need for fake v-sync's except us. I remember asking L1qu1d to add the ability to be able to adjust it several weeks ago which he did. Before it was a static value that couldn't be changed.

[TESTING] Updated 5/14/11 New Kernel - Temp Test - SOD Fix!

Hey kiddos.
WisTilt2 wanted to get some more testers for this kernel, so please download and put it thru the ringer!
This is RHOD ONLY! Please, don't ask if any other devices will work as currently it probably will not! Use at your own risk!
UPDATE 5/14/11 Temp test, SOD prevention!
So the newest autobuild has been plagued with an odd SOD condition. WisTilt2 thinks he traced the issue, and he wants people to run this kernel to see if it's SOD-free (compared to the newest autobuild).
WisTilt2 said:
Current git tree, my pm/fb patch with the proc_comm test. Need to see if anyone gets SOD's. Should have very fast sleep and wakes still, leds are like autobuild also.
Click to expand...
Click to collapse
Let me know guys, thanks!
(In this case, I will leave the old kernel - but do please test this new kernel against the autobuild, see if the SOD's disappear...)
Archive:
UPDATE 4/15/11 SCBS integration
This is the new battery meter code that jonpry has been working hard on. To get the full benefits, you'll need an APK and a new rootfs.img. Please see jonpry's thread on PPCG for more information.
So download this kernel, grab the apk and rootfs from jonpry's thread (don't grab the kernel in his thread!) and follow his instructions if you want to give SCBS a spin. I've already noticed a difference, and I haven't generated a model yet. Rule of thumb with generating the model/algo is the more data the better - so go thru a few charge cycles, some heavy use, some sleep - the more usage the better the algo! Enjoy!
Just to be clear - this new kernel only has the updated SCBS code. Nothing else has been changed since the previous 4/4 test kernel.
UPDATE 4/4/11 Minor fixes...
Just an update to the previous kernel, stylus should be fixed (meaning it will boot into landscape again, fix needs to happen in userland) along with the button lights (when keyboard is open, button lights do not light now). Nothing major!
UPDATE 4/2/11 *Hopefully* failed panel wakes are gone!
WisTilt2 said he found and irq that was set wrong... and it was related to the touchscreen - hence the reason touching the screen wakes it! So this kernel seems to wake very nicely for me - how does it for you?
UPDATE 3/31/11
WisTilt2 said:
This fixes the button lights so they go out when you open kbd and they turn on when you close kbd just like winmo. Also fixed the portrait/landscape unlock screen so at boot it should be in portrait so you don't have to do the back arrow trick to switch it.
Click to expand...
Click to collapse
Update: On the button lights, when the keyboard is open - the button lights will act odd... seems the kernel is torn, it flips them on and then quickly back off .
UPDATE 3/30/11 Button lights, PM Rework, kbd flicker/repeat key, and failed wake fixes!!
WisTilt2 has been trying to clean up his code so he can commit - this is working towards that goal. This new kernel has fixes for the kbd flicker/repeat ("stuck") key bug, the failed panel wakes have also disappeared for me - the panel doesn't always wake instantly, but I've never had to touch the screen to get it to wake - it's ALWAYS come up! Let me know, YMMV as always! Oh and yes, the 4-button light LEDs should now work perfectly as well .
Update - ok, might've jumped the gun on the repeat letter thing - but it does seem better... Just not perfect yet .
RHOD100/AUO users - really need to know if this new kernel breaks your phones! I also would like to know if the SoD issue is actually squashed. I haven't had an SoD in forever, so to those who have recently, let me know!
Perhaps also good to note, is the sleep LED is changed in this one. Initially it will blink green to show that processes are going down and it's trying to sleep (a wakelock of some sort is present in other words). Solid green is full, deep sleep. So you should see blinking green when charging, with GPS enabled etc. You won't get a solid green LED until it's completely sleeping, as usual.
In addition, WisTilt2 has changed the boot screen. Hopefully it'll boot faster, but you'll see a lot less flying text - don't panic! It's normal .
Enjoy! Please feel free to report how this kernel works, so we can get the changes committed!
**Notice**
These kernels are meant for testing purposes - there is no public GIT repo that this kernel code resides on, however the majority of the changes get pushed to the master GIT repo for XDAndroid. The ones that don't didn't work or were simply in place for testing - again the changes that are being tested here are eventually destined for autobuild. Please contact me if you have any technical questions related to this kernel, I will do my best to explain the changes - if you want specifics, I can put you in contact with WisTilt2, the man in charge of pumping out these test kernels. Feedback is not only welcomed but encouraged, please reply to this thread with it!

Downloading and testing now...
UPDATE: Sorry this is taking so long but strangely I've had 5 boots in a row that have resulted in that slow, 100% cpu issue...I've never had that many in a row but can't say that it's the test kernel...I'll keep trying...btw is this built off of the 1245 kernel or an older one?

Yep, testing now.
Incidentally, with both this and 1245 I cannot seem to boot my neopeek system. They fail to see the root partition at /dev/mmcblk0p2 and either hang or reset.
The 1242 kernel still works fine . Weird
Anyway, I will test this out with my XDAndroid setup.
Cheers!

Sorry to be an echo of the others... before I test it, is it built from the 1245 kernel?
1245 seems to be working sweet for me so far....

This should have all the newest commits + WisTilt2's modifications. He said all but bzo's latest commits... I guess git died on him. I'll upload a new one if he builds another.

First impressions on Rhod400:
Speakerphone volume is still fairly low for my taste...when the volume setting is at 1/3 it is barely audible...at full I have to hold it fairly close to hear all words clearly...
Also there is a lot of background "noise" when the external speaker is on...sounds like white noise or static...
Otherwise everything is running smooth...

New Test Kernel (WisTilt2) - 2nd edition - Rhodiums Only
Info: WisTilt2 has another test kernel he'd like some helpful volunteers with rhodiums to test. This test kernel is based on the previous test kernel posted by Arrrghhh earlier in this thread. In addition, it adds bzo's overclock with pm.sleep_mode=1 patch for even better battery life when you're overclocking. So set pm.sleep_mode=1 in your startup.txt when trying this, regardless of whether or not you're overclocking. It also adjusts the volume level of the speakerphone mic to make it easier to hear. Please report any problems you encounter with these kernels, including but not limited, to battery life and speakerphone. Please also mention your rhodium model. They may not all behave the same. Thanks.
WARNING: This kernel is for RHODIUMS only. This kernel could potentially -BRICK- a non-rhodium. So only try this out if you have a rhodium.
Wifi:There is a possibility that rhodium wifi is broken in the stripped version. (WisTilt2 and I use different toolchains. He built it, I stripped it to reduce its size. Our toolchains should theoretically be interoperable, but the resulting modules file is half the usual size. So I'm not entirely sure about that.) If rhodium wifi doesn't work with the stripped version of the modules file, please give the fatter non-stripped version a try. Either way wifi isn't what we're testing here.
Rhodium Only - Kernel & Stripped Modules File(1.94MB version):
wistilt2-kernel-pack-stripped.zip
Rhodium Only - Kernel & Non-Stripped Modules File ("fatter" 8.69MB version, grab this only if you use wifi and the stripped version doesn't work):
wistilt2-kernel-pack.zip

@pdawg17 the static is expected atm, but how loud is it compared to the actual call. same volume or pretty quiet?
People that post here, make sure to specify which model you have, eg. 100, 300. If you don't know you likely shouldn't be testing experimental kernels.

F22 said:
Info: WisTilt2 has another test kernel he'd like some helpful volunteers with rhodium owners to test. This test kernel is based on the previous test kernel posted by Arrrghhh earlier in this thread. In addition, it adds bzo's overclock with pm.mode_sleep=1 patch for even better battery life when you're overclocking. So set pm.mode_sleep=1 in your startup.txt when trying this, regardless of whether or not you're overclocking. It also adjusts the volume level of the speakerphone mic to make it easier to hear. Please report any problems you encounter with these kernels, including but not limited, to battery life and speakerphone. Thanks.
WARNING: This kernel is for RHODIUMS ONLY. This kernel could potentially -BRICK- a non-rhodium. So only try this out if you have a rhodium.
Wifi:There is a possibility that rhodium wifi is broken in the stripped version. (WisTilt2 and I use different toolchains. He built it, I stripped it to reduce its size. Our toolchains should theoretically be interoperable, but the resulting modules file is half the usual size. So I'm not entirely sure about that.) If rhodium wifi doesn't work with the stripped version of the modules file, please give the fatter non-stripped version a try. Either way wifi isn't what we're testing here.
Rhodium Only - Kernel & Stripped Modules File(1.94MB version):
wistilt2-kernel-pack-stripped.zip
Rhodium Only - Kernel & Non-Stripped Modules File ("fatter" 8.69MB version, grab this only if you use wifi and the stripped version doesn't work):
wistilt2-kernel-pack.zip
Click to expand...
Click to collapse
Hey just to report back both kernels do not load it keeps saying that the sd card didn't mount then when I go back to an old kernel it works perfectly so i didn't even get a chance to test the new kernel. Hope it can get fixed so I can start testing for you guys. Thanks and sorry about the bad news

I have RHOD100_de with pm.sleep=1
Well i can say that:
1) The screen is not coming back from stand-by, it remains black while i will nor swipe the unlock pattern (from left to right). It was so on the first stages of kernel with screen turn off feature. UPD: actually screen backlight turns on, but screen doesn’t come back from black...
2) WiFI shows error
3) The in-call/speakerphone volume seems OK
4) Auto backlight function seems to be OK, since it was OK in other kernels.
5) unfortunately currently I don't have enough time to check how battery usage is, i will try to post later.
If You say me on what exactly to focus i'll give more info

So far testing the Rhod kernel:
1) Wifi shows "error" with stripped or "fat" module...I have never had a problem with this on past kernels...
2) In-call volume is great...speakerphone volume is still low to me...the "noise" is lower/better than before but it was be nice for the voice to be a bit higher as in WM it is definitely louder...
3) A couple of times when I woke the phone from sleep the screen was very dim and did not adjust...it was like the auto backlight did not kick in...
4) Sleep mode=1 with my overclock is fine so far...it has woken up all 20 times or so...
5) Occasionally when waking the phone everything is slow/stuttery for a few minutes afterwards...this has occurred the last 3 kernels or so...
I'll keep it running today to see how battery life is...
Otherwise it is great! I'll keep testing!
UPDATE: Just realized my data at some point stopped working too...turning airplane mode on and then off fixed it...
UPDATE 2: Weird...once I did the airplane mode trick my wifi now works AND immediately the stuttering/slowness disappeared and my smooth phone is back!
Rhod400 (Sprint TP2)

Rhod 400. LED is not solid green but occasionally will turn on/off. SOD occured after sleeping for 30 minutes. Speakerphone is much louder but still has static

pdawg17 said:
Downloading and testing now...
UPDATE: Sorry this is taking so long but strangely I've had 5 boots in a row that have resulted in that slow, 100% cpu issue...I've never had that many in a row but can't say that it's the test kernel...I'll keep trying...btw is this built off of the 1245 kernel or an older one?
Click to expand...
Click to collapse
This isn't built off of 1245. I believe it's built off of 1238 with WisTilt2's modifications on top as well as some of the newer patches like 1239 and 1241 added into the mix. I don't believe commits 1243-1245 made it into this test kernel.

Rhodium 100 Panel Issue
solevi said:
I have RHOD100_de with pm.sleep=1
Well i can say that:
1) The screen is not coming back from stand-by, it remains black while i will nor swipe the unlock pattern (from left to right). It was so on the first stages of kernel with screen turn off feature. UPD: actually screen backlight turns on, but screen doesn’t come back from black...
Click to expand...
Click to collapse
Most rhodiums have an EID panel. Some rhodium 100's however have an AUO panel instead. The kernel doesn't properly initialize the AUO panel yet, it only worked before because Win Mo set it up and the kernel never fully turned it off. So now that the kernel is turning it off some rhod 100's aren't waking up. This issue isn't limited to just this test kernel, but exists in all recent kernels. ACL is working on getting the init info for your panel into the kernel. Hopefully it's just the two panels. Should there be a 3rd panel out there it will still be screwed until we can get a volunteer to grab the panel init info from it via haretconsole for us.
2) WiFI shows error
Click to expand...
Click to collapse
Both the stripped and non-stripped versions of the modules file? And are you getting the same stuttery slowness that pdawg17 is experiencing?
3) The in-call/speakerphone volume seems OK
Click to expand...
Click to collapse
Good. That was one of the new things in this test kernel.
4) Auto backlight function seems to be OK, since it was OK in other kernels.
Click to expand...
Click to collapse
Good.
5) unfortunately currently I don't have enough time to check how battery usage is, i will try to post later.
Click to expand...
Click to collapse
Get back to us on that one when you can. That's one of the new modifications that WisTilt2 is specifically testing in this kernel.
If You say me on what exactly to focus i'll give more info
Click to expand...
Click to collapse
Battery.

SD Card Issue
thomas d said:
Hey just to report back both kernels do not load it keeps saying that the sd card didn't mount then when I go back to an old kernel it works perfectly so i didn't even get a chance to test the new kernel. Hope it can get fixed so I can start testing for you guys. Thanks and sorry about the bad news
Click to expand...
Click to collapse
Back up your data via Titanium Backup (downloadable from the market) and try renaming your data.img file to something else. Android will recreate it the next time you boot and hopefully your sd card issue will be gone.

Stuttery Slowness
pdawg17 said:
So far testing the Rhod kernel:
1) Wifi shows "error" with stripped or "fat" module...I have never had a problem with this on past kernels...
2) In-call volume is great...speakerphone volume is still low to me...the "noise" is lower/better than before but it was be nice for the voice to be a bit higher as in WM it is definitely louder...
3) A couple of times when I woke the phone from sleep the screen was very dim and did not adjust...it was like the auto backlight did not kick in...
4) Sleep mode=1 with my overclock is fine so far...it has woken up all 20 times or so...
5) Occasionally when waking the phone everything is slow/stuttery for a few minutes afterwards...this has occurred the last 3 kernels or so...
I'll keep it running today to see how battery life is...
Otherwise it is great! I'll keep testing!
UPDATE: Just realized my data at some point stopped working too...turning airplane mode on and then off fixed it...
UPDATE 2: Weird...once I did the airplane mode trick my wifi now works AND immediately the stuttering/slowness disappeared and my smooth phone is back!
Rhod400 (Sprint TP2)
Click to expand...
Click to collapse
The stuttering slowness means system_server was running amok on your handset. When it goes berserk, it puts a stranglehold on the cpu, preventing wifi and other things from getting their fair share of resources. This issue has existed for months, but it used to be much less common. It appears to be occurring far more frequently in newer kernels with the latest system.ext2.
Thanks for the feedback!

Sleep of Death
vnes1984 said:
Rhod 400. LED is not solid green but occasionally will turn on/off. SOD occured after sleeping for 30 minutes. Speakerphone is much louder but still has static
Click to expand...
Click to collapse
Has the SOD occurred again since? Have you experienced this problem with any other recent kernels? Has anyone else experienced Sleep of Death with this kernel? (Not counting rhod100 users whose panels won't reinitialize after going to sleep. That's a separate issue.)

LOL, thanks for takin care of mah thread F22
Not much for me to do there tho

F22 said:
until we can get a volunteer to grab the panel init info from it via haretconsole for us.
Click to expand...
Click to collapse
Already uploaded to ppcgeeks.
And I did some more testing:
1) I've renamed data.img file and commented lines in froyo.user.conf (from tiad8's 3D Package post) to have a clean system.
2) Tried with stripped modules: Wifi shows error.
3) Deleted this newly created data.img file and tried to boot with not stripped kernel modules: Wifi seems OK.
As told pdawg17 screen lights up, then dim out. Sometimes it is working OK. This behavior exist either with autobacklight enabled or disabled.
Still not enough time to check battery :-(

F22 said:
Has the SOD occurred again since? Have you experienced this problem with any other recent kernels? Has anyone else experienced Sleep of Death with this kernel? (Not counting rhod100 users whose panels won't reinitialize after going to sleep. That's a separate issue.)
Click to expand...
Click to collapse
I haven't experienced this with other kernals. well for awhile. I've since updated to the most recent kernal after the SOD. (working very well btw) It seemed the test kernal had very inaccurate battery readings compared to other kernals. I would hit the power on button to wake and the screen would flicker slightly, it wasn't until I swiped my thumb across the bottom of the screen that the phone would wake up. Once I left it sleeping for about an hour and tried everything to wake it up but no such luck. (rhod400)