yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] snalbansed:
AUO panel not working with new kernel from fresh

Here is an interesting one. At least I think so!

For a good while now I have been running these test kernels on my rhod100_uk with AUO panel, and apart from SODs caused (we think) by poor/changing reception areas, it has been fine. This is with an existing setup that has gone from November 2010 kernels to new ones.

A couple of weeks ago, I tried a completely fresh install of gingerbread - new system image, new data image, latest at the time test kernel, ditto rootfs. I couldn't get it working - it would always SOD within 20 seconds of getting to the home screen.

I then did the same with FRX05 - and had the same result. Didn't have time to investigate, so I went back and upgraded my old setup.

I have now tried again, same result. FRX05, new data.img, F22's latest rootfs, WisTilt2's latest kernel. System freezes within 20 seconds of getting to the desktop.

So I tried an experiment - I swapped the zimage and modules for the one from November 24th. Booted fine (data.img from the failed attempt with everything up to date). Played with it for a bit, no SOD.

Then I swapped the 1st March WisTilt2 kernel/modules back in. Rebooted, and if I had typed quicker, I'd have said it was running fine! However, it has now SOD, but it was alive for ~10 minutes as opposed to the 20 seconds before it had been touched by the old kernel.

So does WisTilt2's new kernel kill AUO panels? I think it might do if it hasn't seen an old kernel! Having said that tomdeaap does seem to be able to use a fresh install everything up to date, until he hits the time bomb of course.

Too confusing!
[Touch Pro2, Tilt 2 Android Development] shatred:
i am using rhod100 with AUO panel.. systems running fine for me, no freeze's ( i tried 8 different builds, frx03 frx04 frx05 gbx0A, latest GB from stine's repo, tiad's blazn, tiad's gingerbread, tiad's froyo red)

they all work with this latest kernel.

only downside so far i have that camera still doesnt work and that the battery life was better with the 26/2 kernel (almost twice battery life i got on that kernel compared with this one)

so i don't think we can blame AUO for your prob. i saw more people having this issues.. to all you guys: be sure to format your sd card correctly and also make sure that there ain't any system backup files on the root of the sd card (these gave me some probs.)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Durn AUO panels...

I say we just remove support for them completely :p.

...Kidding! You guys didn't do any of the cam testing? Oy. There probably is some issue with the new cam code and the AUO panel. I wish you guys would've brought this up to viruscrazy before he committed his cam code, that thread was going for 2+ months...
[Touch Pro2, Tilt 2 Android Development] snalbansed:
BUT he was using main tree kernel that didn't play so well with AUO... so we didn't play until it was too late!
[Touch Pro2, Tilt 2 Android Development] shatred:
i said many times: cam doesnt work on rhod-100
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not sure what you mean... Ugh, I'm getting kinda lost with all the devices and their state to be honest.

Yes, and it probably would if you had helped with the cam testing :rolleyes: This attitude helps no one, especially yourself!
[Touch Pro2, Tilt 2 Android Development] rcgators:
I think he's saying until Wistilt2 got his stuff working, the kernel was not stable enough to use... the cam stuff was too unstable.

Chicken or egg :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well then the AUO panel guys needed to work with viruscrazy to test the cam stuff so it could become more stable...

Kinda hard to help after the fact, now it's going to be a nightmare trying to track down what the problem actually is.

I need you AUO panel folk to step up to the proverbial plate here - if you guys don't give info to viruscrazy, how can he improve anything for your phones? It's literally impossible.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
When I speak for myself I can say that I find the cam much less important then a stable and long lasting phone so that's the reason I put my testing efforts into this one. I did try the cam once, but when it didn't work I thought I did something wrong in one of the many steps you had to do back then.

As for the batt life going down from 28Feb kernel: was that also based on the one that has some of the prepping stuff for the cam in it? If so, it might be that some of that code interferes with the sleep efforts on devices with AUO panels. If only the 3March kernel has any cam stuf in it, the reason for degraded batt life is unlikely to be cam related.

B.t.w. snalbansed has a point: the cam kernel was based on kernels that were very unstable because of random freezing and failed wakes: before wistitls work from the past 2 months I would have left android alone I think. So testing the cam on a kernel that did't work to well in the first place is kind of illogic.
[Touch Pro2, Tilt 2 Android Development] shatred:
I will contact him and give him the logs he needs..
[Touch Pro2, Tilt 2 Android Development] Atmosphere:
I agree. The Camera is a nice to have. A phone which is "maybe on, maybe not" is more of a priority for me. Have a few people phoning me and then getting angry cause i'm "not answering", when in fact the thing is busy having a snooze!
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
Was the 2/26 kernel the most stable out with out the cam stuff in it? If so where can i download it. Thx in advance
[Touch Pro2, Tilt 2 Android Development] shatred:
ignore this*
[Touch Pro2, Tilt 2 Android Development] eik:
Same here. I have been very happy with Wistilt2's work so far: it gave me a phone that runs long on battery (compared to what it used to be) (after 14 hours it is no still on 50%). I am using the most recent kernel from this thread. Sometimes it fails to go into a deep sleep, but waking it and putting it to sleep again most of the time works.

I have only tried the camera once (on 1276) and it didn't work, forced me to reboot to get the phone working again. During the 2 years of WinMo I have only taken 5 pictures or so because I found the quality pretty bad. I guess I am not one of those people waiting desperately on a functioning camera.

Most important for me now is to get more stability; my phone freezes 2 or 3 times a day on average. It is very likely it has t do with the known issue of poor coverage; it happens when I am commuting (train) or walking inside my house. But I understood there is not much point right now to upload logs for that anymore.

--

Rhod100_uk, AUO, Wistilt2 1March krnl, rootfs F22 1March
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I would prefer you don't post old kernels, as that kinda defeats the point of this testing...

Let's look forward guys, not back. It won't help at all testing that older kernel - and if you guys are running these without giving me feedback, just looking for the most stable kernel, then you're really missing the point.
[Touch Pro2, Tilt 2 Android Development] shatred:
sorry, want me to delete the upload?
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
so I went back to the 26/2 kernel with the same data.img, and the freezes that occured after 4 days on the 3March kernel stopped. It'd be interesting to know if they start again immediately if I'd try the 3March again. Will try this afternoon and post results
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
Thanks

Thanks for posting the 2/26 kernel but I forgot I'm running gingerbread system and it wont help cause gingerbread doesnt work with 2/26 kernel so going foward to 3.1 kernel. :o
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Eh, you folks with the AUO panels make me giggle sometimes.

If you want to run it for sanity's sake, that's fine. Just so long as you try to help improve going forward, that's all that really matters.

WisTilt2 has been away, I'm thinking he said he'll be back today tho :D.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
If wistilt solves the bad reception bug, we will have a stable tilt2 with droid. good bye windows!!! actually haven't used windows in about 2 weeks X-)
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
uberz

^

This has been working amazingly on my tilt 2 when reception isn't a problem. Today i ran from 7am to 6pm (11hours) and got down to 15% battery. This is pretty much on par with how the other kernels have ran. I tend to use it 24/7 during this time period reading forums,rss etc in classes (no games). I do notice that it seems to be orange more then before and taking awhile to get to green/wake up. But overall 11hours of basic usage is what i usually get.

And camera even works!

Awesome job!

any way to trick/get Google goggles to work with our build since camera now works =)?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please search before asking questions like this that have nothing to do whatsoever with this thread.

modprobe ipv6 to your froyo.user.conf...
[Touch Pro2, Tilt 2 Android Development] Entropy512:
If you use GPS, you'll still need it around for QuickGPS data loading.

I'm not sure if anyone will figure out the XTRA interface well enough to reimplemented within Android. There's no documentation (although it seems like someone figured out how to sniff the RPC traffic within Windows Mobile in order to reverse engineer the RPC calls needed for location...)
[Touch Pro2, Tilt 2 Android Development] Bieka:
Report of newest Kernel on rhod100_de:

First boot really fast and system seems fantastically smooth. Keyboard Backlight works great and appears with lights off from winmo. I've not yet tested a call but this will come at some point of the day ;). I will test the phone now for the whole day at work (GPS, Calls, GMail...etc). Will report back on todays evening ;) (Remember i'm from Germany and now it's 8:30am ;) so it will last a little longer to report back ;) )
[Touch Pro2, Tilt 2 Android Development] jmstumme:
are there any thoughts about allowing the user to set the timeout from /proc/cmdline?
[Touch Pro2, Tilt 2 Android Development] jchutch2:
EDIT

Wow! All I can say is awesome. This really seems to be working well! Thank you so much for the hard work you guys are putting in!
[Touch Pro2, Tilt 2 Android Development] Raul^:
On my rhod400 (Sprint, on GSM network) all the latest (from 1232 to the newest from 1/1/2011) kernels with modules freeze phone just a minute or so after booting. I'm using newest Froyo.
[Touch Pro2, Tilt 2 Android Development] indigomontoya:
I've done my due diligence in searching, but excuse me if this has been answered elsewhere:

It was not suggested to leave the phone charging overnight in the Oct/Nov kernels. Is this still the case in the recent kernel builds?

Thanks
[Touch Pro2, Tilt 2 Android Development] demonlordoftheround:
It is OK to let the phone charge overnight in Android. I do all the time.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Make sure your system image actually says FRX03. Also, make sure you're using the newest rootfs (still 11/15).

Good to hear the reports guys, I'll pass this info on to WisTilt2! I'll keep updating this thread whenever I get new kernels!
[Touch Pro2, Tilt 2 Android Development] Raul^:
As I wrote before i'm using latest FRX03 (from XDAndroid2.2.1.FRX03.Froyo.121110.zip package).
[Touch Pro2, Tilt 2 Android Development] toadlife:
FYI,

When first testing I got the wifi error issue. It seemed to be caused by leaving the old modules* package in my andboot directory. It looks like it was unzipping the old modules package first, causing the old modules to be used instead of the new ones.
[Touch Pro2, Tilt 2 Android Development] Bieka:
So here is my report for a whole day using the newest kernel.

First: This Kernel is the fastest i ever had. Apps apply as quick as never before. With Google Maps/Navigation running i get 100%CPU Usage but that's ok cause it runs smooth.

Second: Speakerphone and Mic are working great and Volumecontrol is working well. No reboots, no problems just working ;).

Third: I noticed that after some navigation with different apps there are some problems. In Google Maps the phone completly restarts without a freeze, sluggish navigation or something. Just out of navigation the phone restarts and boots into winmo. In Navigon Mobile Navigator there are app restarts and freezes. In all GPS using Apps there are problems getting a GPS Lock after some running time. Fresh booted i get a GPS is lock within seconds but after one route and and a time staying at this point (closing the Navigation app and going to serve my customers for about an hour average) i don't get a GPS lock within 30 Minutes... after this time i started closing the apps and deactivate/activate GPS, starting Navigation again, close them again, deactivate/activate GPS, Activate WLAN, starting the app..... after some time i get a GPS lock then but thats the hard way ;). Any Ideas if this is because the TP2 GPS Module is kind of scrap or is it a android/module/app issue?!

Fourth: Data/Wifi/Phone is working very well.

Fith: Battery lifetime seems ok. But I can not say for sure because I had the device on the charger during the navigation.

Keyboard Backlight also works great without flickering.

All in all it is a good working Kernel.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I mean actually check to see if that image is FRX03. There's a lot of stuff flying around...

Settings -> About Phone -> Build Number.

Great report. As for your GPS issue, I'd only repeat that QuickGPS should be used before booting Android. Nothing in this kernel *should* have any effect on GPS whatsoever.
[Touch Pro2, Tilt 2 Android Development] Bieka:
Thanks arrrghhh,

i will test that ;). Does this last longer for GPS or does this only last some time?

I will report back if any other things can be noticed ;).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Supposedly QuickGPS download data is good for 7 days, but as with most things, the more up to date it is, the better. I basically run QuickGPS before I boot Android if I know I'm going to be in Android for more than a few minutes :p
[Touch Pro2, Tilt 2 Android Development] Bieka:
So i just wanted to do a quickgps fix but i've noticed i'm running the Stripped Energy Rom without QuickGPS. I searched for a download to get Quick GPS installed but didn't found a link that is not dead :-/. Does anybody have a cab for me?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Here ya go. I know it says, "with patch" - no clue what that means. Original post for reference.
[Touch Pro2, Tilt 2 Android Development] Bieka:
Thanks a lot
[Touch Pro2, Tilt 2 Android Development] JBS2:
Using the 1/2/2011 kernel for a few hours now. Fastest kernel ever, keyboard backlight is working great :)

Anyone using another navigation then Google Maps Navigation?
[Touch Pro2, Tilt 2 Android Development] Bieka:
Yes, as i said before i'm using Navigon Mobile Nagigator Selevt (3.5.2). But it restarts often. I use Navigon since the Trial Version 2.6.1 and on Android before having sound ;))) It is great. It gets the Traffic over the data connection so you have TMC like navigation, also it has TTS, Sign Assistant (Speedlimits, Attention Signs etc.), Radarcontrolls (don't know if this is the right english word for what i mean ;)) ), and many other features. The best thing for me is the Google Search within the App. I got many Customers like discounters and supermarkets and i only have to search for the market name and city and i can choose from a list of found markets. Navigation to contacts and favorites are also implentet so it is a very useful app. Only the restarts are making me crazy ;) I will try a fresh install in the next few days. If you are interested in it write a PM for more Informations ;).
[Touch Pro2, Tilt 2 Android Development] AkumaX:
i'll 2nd that. great speed on this update! (1/2/11)
[Touch Pro2, Tilt 2 Android Development] gnnash:
Keyboard backlight working great now! I am having one problem though...

When inputting text, sometimes certain letters seem to get "stuck" for a bit. For example, if I type "light" it may input as ligggggggght. The key isn't physically getting stuck, it just seems that the CPU gets loaded for a bit and just keeps repeating a letter.
[Touch Pro2, Tilt 2 Android Development] ivwonka:
I think GPS Status is free in market and can download this same aGPS data.

Sent from HD2 hyperdroid gingerbread
[Touch Pro2, Tilt 2 Android Development] manekineko:
Unfortunately, GPS Status doesn't seem to actually link into our GPS's on either Touch Pro 2's or HD2's.
[Touch Pro2, Tilt 2 Android Development] the.decoy:
Yes, the new sleep code is great when I have good reception but unfortunately I work in a 100yr old sandstone building and likewise my home is on the side of a massive hill (low signal shadow) ... so I always end up with an SoD eventually.

However the last 2 days I made a point of keeping the phone awake when traveling through the particularly bad signal black spots, and I noticed something rather interesting ...

After roughly 6hrs on both trials I ended up in a "No service" state and even thought phone hadn't SoD'd on me it didn't matter because nothing I could do would get signal back. Trying to toggle in/out of Airplane mode just fails or locks up the system.

I was curious what version Radio ROMs everyone is running on their GSM rhods?

I am on 4.49.25.77 , and I know there is a 4.49.25.95 but that is from ATT whereas .77 is actually from Telstra and specifically intended for the RHOD110 that I have.

I am willing to experiment with a few other radios but just wanted to see what everyone else was using.

Cheers!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I have 4.49.25.57 on my T-Mobile US Rhod 210. I wonder if upgrading it would make any difference, not likely.

At this point as long as I leave data disabled, it never hangs.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Iv experience the same behaviour as the decoy, attempting to switch in and out of airplane mode doesn't work correctly. Also attemting to 'search for networks' usually results in a full freeze up of the fone and innevitably I'm forced to reboot to get a signal.

Also still using FRX04 For testing, but on the matter of problems with partition(neopeek) builds iv found the problem is modules related . . Renaming the modules so they are not installed solves all problems (except obviously disables wifi and such)
[Touch Pro2, Tilt 2 Android Development] Entropy512:
In addition to support from the application, the driver needs to support the interface.

In our case, due to lack of documentation on how to communicate with the chipset, these functions in the driver are nonfunctional stubs - they return successful status without doing anything.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Another interesting find on my AUO rhod100...

With my fresh FRX05/latest F22 rootfs/1st March WT2 kernel build, after temporarily using the 24th Nov kernel to get it going, I haven't had many SODs at work.

Previously I would have half a dozen a day - at least.

Until today, when I setup my corporate Exchange email again. SODs returned with avengance. So I changed the check frequency from push to never. More SODs. So I removed the account. All was well again! I've had one SOD since, but about 7 hours after I removed the email account.

So this may have nothing to do with AUO/EID, but something about Exchange email in dodgy signal areas on my rhod100 doesn't go.

I otherwise have 5 gmail accounts syncing. 5 gmail plus Exchange was always fine with the old Nov 24th kernel.

I hope this is somehow useful info :)
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Were these true sods {green LED), or freezes with orange LED?
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
My rhod100_de is very slow with this actual kernel, not possible to work. B4home is also not working. The keyboard is very slow. Is is not possible, to write the pin, because I have double and more digits if I press one.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What system image are you testing this on, FRX05?

Also, have you tried with a normal autobuild rootfs? Sounds like you're using F22's rootfs. Just want to rule that out.

In the spirit of ruling things out, I'd also like you to try a new data.img. If you're concerned about recreating everything, you can simply rename your data.img so you can easily revert to it!
[Touch Pro2, Tilt 2 Android Development] snalbansed:
I don't remember with certainty, but I suspect the majority were probably panel off, orange LED.
[Touch Pro2, Tilt 2 Android Development] toadlife:
All of my SODs have been with an orange LED.
[Touch Pro2, Tilt 2 Android Development] toadlife:
Phenominal batery life

*duplicate post*
[Touch Pro2, Tilt 2 Android Development] toadlife:
Phenominal batery life

4:23PM and 87% battery! Took it off the charger at 7:20AM.

Phenomenal!

Using FRX05/03/01 F22 rootfs and the 3/01 wistilt2 kernel

EDIT: And NO SODs in days since disabling data.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
I think we may have finally found a way to get good debugging info. I think some of the "death" situations and this one are related. Many of my "deaths" are orange-LED ones.

Today I left the phone on the charger most of the day at work. Sometime this afternoon, the phone went to "no service" and stayed there.

Unlike you, when I got home I was able to reset things by entering airplane mode and exiting it. NOTE: I did it from the launcher screen by holding down power. I've noticed I get different behavior in terms of entering/exiting airplane mode when I do it from Settings on both this and my Huawei S7. (In general, not this specific situation.)

While the phone was in "no service" state, the phone lost ability to sleep. Wakelocks in SMD_DATA1.

I managed to get dmesg and radio/normal logcats, and a second radio logcat after resetting the radio (see above) - I'll post them when I get home. (I had to run out the door.) (EDIT: Attached) On first review, it seems to be a situation related to having an active data session when we transition to an unregistered state - which jives with the one person who hasn't had a problem since disabling data.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Two people. Myself and toadlife.
[Touch Pro2, Tilt 2 Android Development] manekineko:
FYI, this test kernel works for touch screen calibration, which was broken in the mainlines for a while, because it outputs a lot less junk during bootup which normally overwrites the display of the calibration.
[Touch Pro2, Tilt 2 Android Development] Quincux:
My SOD are with orange and green LED :confused:
[Touch Pro2, Tilt 2 Android Development] toadlife:
I'm not 100% positive that *all* of my SODs have been with the green LED.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Don't mean to be splitting hairs here, but I was under the impression that a freeze with a green LED (SoD) was quite different from a freeze/hang with an orange LED. Not sure, but it might be good in order to get clear what we're talking about here.

I haven't had the first in weeks; the latter however I have once or twice a day; usually behing my desk where there is good service. I'm kinda used to it now and don't think too much of it, I just reset and carry on. But obviously if possible let's get these out of the way as well! I noticed a huge increase in the orange freezes (sounds like an icecream :D) when I use calendar widgets (which obviously syncs with google). I might try today with cal widget, but without data, see if that cuts down on the orange freezes.

Again, if you we're talking about a true SoD, this idea might not make sense at all :D
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
After a fresh install on a new sdcard the system (frx5) ist running fast.
[Touch Pro2, Tilt 2 Android Development] Eodun:
O_o

Wow, I'm jealous :P Congrats!
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Indeed - 6 hours and 50% for me :(

Including one SOD.