Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,781,289 Members 36,153 Now Online
XDA Developers Android and Mobile Development Forum

[TESTING] 3.3/3.4 kernels

Tip us?
 
detule
Old
(Last edited by arrrghhh; 13th October 2012 at 03:25 AM.) Reason: Modified links since autobuild is down...
#1  
Senior Member - OP
Thanks Meter 332
Posts: 300
Join Date: Jan 2010
Default [TESTING] 3.3/3.4 kernels

Let's make life less complicated and start a new thread for people to provide feedback on 2.6.39, ... 3.3, 3.4 (NEW) RHODIUM kernels. The source repository is here. Note, older trees are not under active development.

By the way, these kernels are developed jointly with jonpry, WisTilt2, and bzo. In addition a lot of code is shared with people that maintain active msm kernel branches (emwe, acl, Alex). Finally, all Xdandroid Kernel developers have in one way or another contributed code.

1. Feel free to use any of these kernels, however DO NOT submit a post in this thread that amounts to "This feature does not work for me." If you wish to submit a bug report, make sure you are proficient at using ADB, AND have installed GetLogs. In your post you should:

a. Include GetLogs output of the problem (or it didn't happen).
b. Include Rhodium model (100, 210, etc).
c. Try to reproduce the problem on the other kernels.

All other bug reports will likely not receive full attention.

2. These kernels are to be used with GBX0B.

3. These are auto-built at:

Auto Built Service generously provided by WisTilt2

The autobuild is down. Please use these links, they were the final kernel builds that were on the autobuild site.

2.6.39.3
3.0.18
3.3.8
3.4.3

4. What works:

This list should look very similar to the current status of .27 with your device. Meaning, if you have a rhodium on which the camera does not work with .27 (for example), camera will not work with these kernels as well. Please do not report issues that are present on .27+your device.

- Only 3.0 has BT support. Would appreciate some feedback on this. I get the impression that pairing/connecting takes a bit of patience, but I am interested in how this compares to BT in .27. If we get some positive feedback we can enable BT support across all three kernels.

5. How do these three kernels differ: They are maintained by the same group of people, and consequently differ very little. There are slight variations in power management code, but other than that they are hard to distinguish in terms of functionality.

6. Kexec: To hot-swap the kernels (boot with a new kernel without rebooting into WinMo):

a. While in Android, copy the new kernel and modules to the same location (over-writing the zImage) as your current kernel (adb push).
b. Go to the shutdown menu in GB, and select "Kexec".
c. Phone will reboot within Android, using the new kernel.

7. Finally, I don't have too much time to hang around xda, so you shouldn't hope for "next-business day" response policy I am just hoping we can attract the advanced user to these kernels, that can do most of the troubleshooting on their own.

Enjoy, RHOD has to be one of only a handful of android devices that are pairing android with kernels as advanced as these.
The Following 11 Users Say Thank You to detule For This Useful Post: [ Click to Expand ]
 
detule
Old
(Last edited by detule; 19th June 2012 at 06:29 PM.)
#2  
Senior Member - OP
Thanks Meter 332
Posts: 300
Join Date: Jan 2010
This you should note:

I. If you are experiencing problems with turning Wi-Fi on, try the procedure outlined HERE before posting.

II. With regards to usb related functions and 3.4:

This kernel uses ICS style usb drivers and as a consequence, usb notifications in GBX no longer work. To work around this issue we wrote a little app XdaRndisToggler, which should allow you to turn on ADB, as well as USB Tethering (RNDIS).

Using this app is pretty self-explanatory:

0. Plug your phone in (No notification will appear in GBX).
1. Start the app.
2a. To start the ADB service, select "ADB only" and click apply. At this point you can use ADB to connect to the device.
2b. To start USB tethering, select "ADB+Rndis" and click apply. At this point go into Settings->Wireless->Tethering and check the box that says USB Tethering. The blue "USB Tethering" notification should appear in your taskbar and you should be all set to tether.
3. To stop using ADB and/or RNDIS, select "Disable USB" in the app and click Apply.


FOR ADVANCED USERS:

Alternatively, you can use ADB without the use of XdaRndisToggler (app is still needed for tethering), by making the following changes to init.cfg/init.gingerbread.rc (note, you will need to remount / as rw)
Code:
 
 on property:persist.service.adb.enable=1
-    start adbd
+   start adbd
+    write /sys/class/android_usb/android0/enable 0
+    write /sys/class/android_usb/android0/idVendor 0x0bb4
+    write /sys/class/android_usb/android0/idProduct 0x0c01
+    write /sys/class/android_usb/android0/functions adb
+    write /sys/class/android_usb/android0/enable 1
 
 on property:persist.service.adb.enable=0
     stop adbd
+    write /sys/class/android_usb/android0/enable 0
+    write /sys/class/android_usb/android0/bDeviceClass 0
Above, minus/plus is used to denote delete/add line respectively.

Downloads:
XdaRndisToggler 06/19
The Following 2 Users Say Thank You to detule For This Useful Post: [ Click to Expand ]
 
ryannathans
Old
#3  
Senior Member
Thanks Meter 47
Posts: 294
Join Date: Dec 2009
Location: Perth, Western Australia

 
DONATE TO ME
Ts-calibration is not working on the 3.0.9 kernel.

I can't see the [+]'s.

I was forced to use my own calibration file.
Quote:
Originally Posted by arrrghhh
Put on your big boy pants, this is the Internet (that's right, capital I ).
 
marcopolo
Old
#4  
marcopolo's Avatar
Senior Member
Thanks Meter 78
Posts: 355
Join Date: Apr 2009
I am using the temporary 3.0 kernel and till now, I have faced a few problems:

1) Whenever I make a call, the screen goes blank (I couldn't get the logs using Getlogs, don't know from where to pick it) possibly because of the proximity sensor, the screen won't back even if I use power button, however if I slide out the keyboard, the screen comes back.

2) On some random calls, the sound simply gets disappear and doesn't come. Normally this doesn't happen on every call (trust me, I called more than 7-8 phone no. for more than 1 hours today itself) but suddenly, but on one call, the sound just vanished and I couldn't hear anything from the caller on the other side. The problem remained there until I rebooted my phone.
 
detule
Old
#5  
Senior Member - OP
Thanks Meter 332
Posts: 300
Join Date: Jan 2010
Quote:
Originally Posted by apurohit View Post
(I couldn't get the logs using Getlogs, don't know from where to pick it)
GetLogs
 
detule
Old
#6  
Senior Member - OP
Thanks Meter 332
Posts: 300
Join Date: Jan 2010
Quote:
Originally Posted by apurohit View Post
1) Whenever I make a call, the screen goes blank (I couldn't get the logs using Getlogs, don't know from where to pick it) possibly because of the proximity sensor, the screen won't back even if I use power button, however if I slide out the keyboard, the screen comes back.
Also, since it seems this is an issue you can reproduce (which rhodium by the way?), can you try some of the other kernels .35, .39, 3.1 and try to reproduce it there as well.

Are you using 3.0 for its bluetooth capability - if so, how's that working for you?
 
marcopolo
Old
(Last edited by marcopolo; 6th January 2012 at 05:28 AM.) Reason: Attached Getlogs
#7  
marcopolo's Avatar
Senior Member
Thanks Meter 78
Posts: 355
Join Date: Apr 2009
Quote:
Originally Posted by detule View Post
Also, since it seems this is an issue you can reproduce (which rhodium by the way?), can you try some of the other kernels .35, .39, 3.1 and try to reproduce it there as well.

Are you using 3.0 for its bluetooth capability - if so, how's that working for you?
Well, I tried pairing bluetooth with my laptop and a bluetooth headset, it takes forever however my laptop and the headset is always visible in the available device list. I have used .39 (wifi wasn't an issue on it but calls were problem) and .27 (provided with the bundle where voice issue was constant) and then used 3.0 (temporary provided by you), I am facing this problem on all of them. I have RHOD100, CSVs are attached with this post.

Also, I already have getlog installed on this build (it was provided in the Android App folder) but still, I cannot figure-out where exactly it is saving the file. Since you have provided the Getlog thread hence I will read it through and will provide you the same.

Update: Have attached logs taken from Getlogs. Thanks for the guidance.
Attached Files
File Type: zip RHOD100.zip - [Click for QR Code] (25.9 KB, 150 views)
File Type: rar Getlog_RHOD100.rar - [Click for QR Code] (38.1 KB, 66 views)
 
detule
Old
#8  
Senior Member - OP
Thanks Meter 332
Posts: 300
Join Date: Jan 2010
Quote:
Originally Posted by apurohit View Post
Update: Have attached logs taken from Getlogs. Thanks for the guidance.
You instincts were right, it is proximity related. In the file you attached if you search for "proximity" you will see a few "proximity 0" and no "proximity 1" -> meaning the proximity sensor is always reporting "user is near" and consequently the screen stays off.

Here is a silly question, do you have a case on your device, one that might be obstructing the sensor?
The Following User Says Thank You to detule For This Useful Post: [ Click to Expand ]
 
marcopolo
Old
#9  
marcopolo's Avatar
Senior Member
Thanks Meter 78
Posts: 355
Join Date: Apr 2009
Quote:
Originally Posted by detule View Post
question, do you have a case on your device, one that might be obstructing the sensor?
Nope, I don't have one. In fact I have been facing this problem in the Windows Mobile ROM also... but used some tweak. This problem was not there in the FRX07.1 and the screen was good however I am now facing this with GBX0B which is not a new thing.

The screen comes back the moment I pull hardware keyboard but goes off if the call is on or I press power button (general practice to turn the screen on) and then it won't come even if I pull the keyboard.

I have one more question which may sound off topic but thought it's good to ask an expert rather suffering forever.

I am wondering which key should I use to disconnect the call since the end key doesn't work in this case and throw me back on the home screen.
 
detule
Old
#10  
Senior Member - OP
Thanks Meter 332
Posts: 300
Join Date: Jan 2010
Quote:
Originally Posted by apurohit View Post
Nope, I don't have one. In fact I have been facing this problem in the Windows Mobile ROM also... but used some tweak. This problem was not there in the FRX07.1 and the screen was good however I am now facing this with GBX0B which is not a new thing.
Yes, GBX0B is the first time (apart from NAND) that proximity-related functionality has been enabled.

If you are seeing the same problem in WinMo then you may be facing a hardware failure of your proximity sensor. On the other hand it could be that RHOD100 is somehow special, and we don't have the correct gpio setup in the kernel to handle your device. I just heard from a RHOD110 user saying that everything is fine, so I might be leaning towards the former.

Unfortunately I don't know of any quick tweaks to disable the sensor in Android.

The Following User Says Thank You to detule For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes