This thread is dedicated to the development of the 2.6.35 kernel for the Xperia X1 (HTC Kovsky) device.
Alex (sp3dev) has done a wonderful job so far to port a lot of his pervious 2.6.27 work into this branch. His source code can be found here: http://gitorious.com/~ast/linux-on-qualcomm-s-msm/alex-linux-xperia
It’s possible to build the source and boot the kernel, but no functionality beyond that is functioning so far (i.e. it won’t connect to your GSM network or be able to detect touch on the screen).
Eventually releases will be posted here; hopefully other developers can submit patches, recommendations, etc.
Thanks, and stay tuned!
Great, expecting the completely new kernel!
Stay Tuned, YES!!
seandean said:
This thread is dedicated to the development of the 2.6.35 kernel for the Xperia X1 (HTC Kovsky) device.
Alex (sp3dev) has done a wonderful job so far to port a lot of his pervious 2.6.27 work into this branch. His source code can be found here: http://gitorious.com/~ast/linux-on-qualcomm-s-msm/alex-linux-xperia
It’s possible to build the source and boot the kernel, but no functionality beyond that is functioning so far (i.e. it won’t connect to your GSM network or be able to detect touch on the screen).
Eventually releases will be posted here; hopefully other developers can submit patches, recommendations, etc.
Thanks, and stay tuned!
Click to expand...
Click to collapse
yes, I think we have to use this thread to stay up to date with the kernel development.
My opinion is that there are few developer that continue to port android on kovsky, the Alex branch is one the most active. So I'll follow you.
Thanks and keep going.
OK starting with the offtopic in development thread again (sorry), but what are the advantages of the new kernel?
Mainly to clean up the code and iron out bugs (probably to merge with mainline linux one day).. But anyway, just for fun..
Alex can you just do some quick fixes and compile .35 version for NEOPEEK GINGERBREAD ROM ???
That's would be great thing for X1 community
no, unfortunately not. it requires much more than small fixes. porting microp and touchscreen drivers is a huge PITA. and i want to port some nand bootloader first
Ok thanks for answer...
But, i didn't understand what you mean by that bootloader...you wanna make DIRECT NAND ADROID BOOTLOADER for X1 ?
Anyway is that what you love to do or you know how to do it ?
If you need any help from me i am here. I am not good with LINUX terminal, but i know VB.net, C#, and a little C++.
Thanks for everything rusian brother
This looks like the stuff they are doing here https://www.codeaurora.org/gitweb/q...it;a=shortlog;h=refs/heads/android-msm-2.6.35, whats different?
Ok, a very experimental zImage. Only for those of you guys that have much free time and nothing to do...
http://www.mediafire.com/?a1rzi5embishqd7
It contains:
kernel 2.6.35.7
Working:
Touchscreen
Sound/headset (with the new libraries from jbruneaux). You need to copy AudioFilterTable.csv, AudioPara3_XC.csv renamed to AudioPara3.csv, AudioPreProcessTable.csv from \Windows to the root of sd card. All in all, this means you can use custom acoustic tables and sound quality will improve greatly.
LEDs. Completely reworked, doesn't hang with custom triggers. Do 'echo mmc0 > /sys/class/leds/green/trigger' to have fun and let the green led blink like on your desktop when accessing sd card.
Phone calls (huh. i have not tested mic though)
Keyboard/keypad.
USB - will probably fail if booting with usb plugged. replug to activate. some power management was reworked (will need to fix that glitch with booting with usb in), but now the power of ulpi is disabled when usb unplugged - less drain
Battery monitor/Charger - less hackish now. Uses linux power system to drop voltage/monitor charging. The charger status updates instantaneously on plug/unplug
Shutdown/reboot
Not working yet:
GPRS/PPP (alright.. you are free to fix the userspace, ril and scripts to choose the correct smd channel. i will not add the hack swapping channels 1 and 7 to the new kernel)
GPS (will just crash. but probably more a userspace thing, though)
Bluetooth (rfkill is there. it will hang dead if you try to access the serial port, though)
WiFi
Qwerty backlight (i'm just lazy)
Vibra (look up the previous point)
Camera (WIP)
Optical Joystick
To make sound work, copy the two .so files to /system/lib. They are incompatible with previous kernels (htc-linux tree) and vice versa, this kernel is incompatible with the old libraries.
Do NOT set pm.sleep_mode to 0 or 1, it is not yet working
So, you can see that this is highly experimental and a WIP, it's more a proof of concept, but if you have time, you could try it to see if it boots for you..
I guess like everyone here... i just want no more button freezes! everything else is currently working acceptably for me!
Wow, amazing you managed to get 2.6.35 working on our mobile phones, I like what you have done with the LED's And reponse time was impressive and it felt very speedy, had sadly some issues that prevented me from running any benchmarks.
Honeycomb is not working will with this new kernel, could not connect to any network, it was continiously switcing flight mode on off preventing any kind of network from working. Could not browse the filesystem with included filebrowser, I do wonder why as I had not problem accessing /sdcard from a terminal.
Do you know why the existing froyo libraries have problems with the updated kernel?
No, i have no problems. Ril works fwiw
http://img441.imageshack.us/img441/6028/devicefn.png
So, maybe you need to do a wipe before booting. Anyway, it is nowhere near working, so i guess it is pointless digging into the userspace before getting all hardware on 35.
One thing. JB sound libs may be prelinked and conflict with your system libraries, so i think it's best to wait until this stuff is merged to xdandroid first
Was this kernel made based off source changes not yet committed to GIT? I tried last week building a kernel based on your 35 repository (which it built successfully) but the touch screen wasn’t working for me.
The touchscreen part was not modified, but yes, some of the code is not yet released. I am still working on headset and audio and plan on committing it later this week. I am now testing wifi. The card seems to bring up now, but i have not yet tried connecting. Setting up debian chroot for that now
But Alex,
Please understand that all kernels from .27 series have really unstable WiFi and really slow... If you can make WiFi to work like on WM that would be all what i want in Android
Thanks
It is really great work guys .. keep it up .. i'm waiting for this kernel ..
hope i can see it fully working soon .. as i guess it may overcome libskia problem as neopeek said .. which will give us the ability to port many awesome roms ..
Thanks too much Alex & Seandean ..
sp3dev said:
The touchscreen part was not modified, but yes, some of the code is not yet released. I am still working on headset and audio and plan on committing it later this week. I am now testing wifi. The card seems to bring up now, but i have not yet tried connecting. Setting up debian chroot for that now
Click to expand...
Click to collapse
good work!!! what about FM Radio and front camera in the future?
Wow. after much trial and error, wl1251 'just works' as it should (well, actually the wl1251 sdio driver is a bit buggy, so for some time now we won't be using wifi interrupt and power saving mode). The patches for mmc are commited.. The rest, audio and headset, will come later
sp3dev said:
Wow. after much trial and error, wl1251 'just works' as it should (well, actually the wl1251 sdio driver is a bit buggy, so for some time now we won't be using wifi interrupt and power saving mode). The patches for mmc are commited.. The rest, audio and headset, will come later
Click to expand...
Click to collapse
Excellent, sounds like 2.6.35 is getting close to replace the old 2.6.27
Do you have some precompiled wpa_supplicant and libnl.so that are working with the wl1251 network driver? Have added the compat-wireless to the old 2.6.27 but I am having some difficulty compiling the tools needed to control it and verify if it is working at all on the old kernel.
Downloaded a copy of your 2.6.35 source yesterday, can see that I allready now need to download it again to get your latest updates
Hello All,
Have just started using this forum and failed to introduce myself previously, my name is Jay; I am 27 from DC but in Afghanistan for a few more months (yea..sucks) new to rooting, flashing and all that but I have recent interest in it and it passes the time better than most thing we are "allowed" to do over here.
I just switched from a HTC Desire to a Galaxy Captivate
So far...I have unlocked it (via cellunlocker.net), upgraded to the leaked 2.3.4 Gingerbread, Rooted using the 10step method posted here, Installed Victory v1.5 Rom, tried flashing Talon kernel but bricked the phone and had to redo the above...
My question is to those more knowledgeable than myself with all this...what is the best Kernel, Rom, Modem...whatever else...that I can have on this device to keep it running smoothly, fast and reliable?
I do all the basic call, txt, surf...play games, watch movies, use apps, etc...not a developer but want my phone to be tweaked as much as possible so it does not seem outdated or lag with new things being added.
My current settings are:
Baseband I897UCKH3
Firmware 2.3.4
Kernel 2.6.35.7-I897UCKH3-CL461307
Build VictoryRom_v1.5
There is nothing wrong with the phone...as I said above, if I could do more to it and have an overall better device and pass some time here I would enjoy that. Victory seems great but all I notice myself is the battery indicator has changed and...thats about it (a lot likely goes unnoticed by me)
I do have one problem with the phone that maybe a different modem can fix? (I hope) for some reason my GPRS will not work out here with my browser...I can use the market and apps that connect to the internet but my browser seems to be WiFi only. I have changed the settings from usa to europe since I am using a sim from over here but no luck...and added the gprs settings to the phone which allowed apps internet access but zero for browser..any ideas?
I really thank anyone who takes the time to reply...I am sure teaching a new person in this is annoying just as showing the new guy here how to clean his weapon...lol...but we were all new at everything once and I thank you all for reading my novel
-Jay
Jay,
Thank you so much for your service and contribution to our freedom, I know it must be hard to be away from the life you once knew. Hang in there It's not for nothing. Hopefully someone will be able to help with your GPRS settings. I am running the same setup on my captivate only I have used Boogs kernel to install clockwork recovery as well. You can flash boogs kernel over the kernel you have now and that will let you flash roms or speedmods later. If I were you I'd keep my eyes peeled for GPRS settings in your area and wait for EXT or speedmod kernel for the 2.3.4 They are saying RFS is pretty quick to begin with though. It may be hard to beat but im sure one of these great Devs will figure out a way to make 2.3.4 smokin fast. Once again thanks for doing what you do. Keep your head down Soldier!
Steve
If you like using your mobile providers Net, you might give I9000 ports a try. They allow for better Upload speeds but you will sacrifice Audience chip support (noise suppression processor that only I897 have). Also since I9000 source usually drop first they have all sorts of kernel mods like Voodoo sound, Voodoo color fix, BLN, init.d files tweaks like V6, among many more. Sadly I897 native roms always play catch up with I9000's.
Personally I prefer native rom, because they tend to run smoother for longer periods of time (I9000 tend to slow down over time on my phone, but thats just my experience) and I don't use ATT's network a whole lot (90% of the time I'm around a wifi connection) and I like the audience chip, it is a phone before anything else.
Edit: Also there isn't a "best" rom, kernel or modem. Each rom has their own pros and cons, same as Kernels. And no 2 phones are the exact same so not all of them take well to all the tweaks, mods, etc. And most of the time i9000 kernels wont work with i897 roms, at least in GB.
first of all, sorry about my bad english
well the thing is that i have problems when i try to update my i897 to ICS or JB. Every single time i try my screen turns blue after the initial AT&T logo. I have tried several kernels/roms but always get the same result. I have made a video of the problem:
www dot youtube dot com/watch?v=wwMqqMJK7cM
Does anybody knows how to fix this? i have found a video of someone with a i9000 with the same problem
www dot youtube dot com/watch?v=rMStfVEOo6c
it seems that i cant post links because an xda spam policy -.- copy and paste the watch/ part on youtube to see the videos
I have the same problem as well. Seems it's not limited to i897 only. It happens with i9000 also. Supposedly it's related to using Nexus S framebuffer for our devices. Most kernels seem to have implemented that and therefore some devices with incorrect calibration data seem to run into this problem.
I even tried to use Glitchy kernel with CM7 and had the same problem. The kernel that comes with CM7 by default works fine.
I tried SlimBean and LANIGHT rom's also and had the same problem.
Hope the kernel developers fix this issue or release versions without the Nexus S framebuffer implementation. Or if someone knows of a kernel that doesn't use Nexus S framebuffer but supports CM9 and other ICS & JB rom's.
You might want to update the title of the thread to give more details of the problem and hence attract more attention from the developers hopefully.
I haven't updated my SCH-I800 in a while and I notice that there is now a stable "cm-9.1.0-p1c.zip" on the cyanogenmod site but also CM10 builds (cm-10-20130714-NIGHTLY-p1c.zip) as recently as last week. The forums for the I800 aren't up right now so I thought I'd ask here if these CM10s are actually functioning well or if they have lots of missing features. And as much as I dig, I seem to only find half working ROMs or extremely experimental ones that have basic things like WiFi missing. Is there a solid stock Samsung ROM and a solid AOSP ROM that everyone uses at this mater point in this tablet's lifespan?
And is there a new method for flashing at all? Or is ODIN still the way?
Thanks!!!
tinpanalley said:
I haven't updated my SCH-I800 in a while and I notice that there is now a stable "cm-9.1.0-p1c.zip" on the cyanogenmod site but also CM10 builds (cm-10-20130714-NIGHTLY-p1c.zip) as recently as last week. The forums for the I800 aren't up right now so I thought I'd ask here if these CM10s are actually functioning well or if they have lots of missing features. And as much as I dig, I seem to only find half working ROMs or extremely experimental ones that have basic things like WiFi missing. Is there a solid stock Samsung ROM and a solid AOSP ROM that everyone uses at this mater point in this tablet's lifespan?
And is there a new method for flashing at all? Or is ODIN still the way?
Thanks!!!
Click to expand...
Click to collapse
I have spent the last week or so trying to get an SCH-i800 to run something OTHER than the stock gingerbread well and just haven't found it yet. The closest I got was a build of CM9 but still have sporadic reboots.
It's frustrating since the only thing I want this to do is run some OBD apps for my car. The problem is that apps detect Gingerbread and run in phone mode vs. tablet mode, wasting a bunch of screen space.
Cubed has been pretty much the only non-stock rom that didn't have FC's and random reboots. I don't even use the cellular feature of this tablet - I'd be happy just disabling the modem entirely and running on wifi if it meant it being more stable.
I'm considering just getting a Nexus 7, but the problem is that this thing would need to live in my car and I don't feel like doing that with a new tablet which is why I was trying to get the i800 to work
The title may look weird but that's the best sentence I could find to summarize my question.
One of the myths about mobile phones is that they have back doors for the secret services or goverments to tap into and listen to phone calls or SMS messages. This was something we could never be sure about at the old days of Nokia (R.I.P.) "black box" phones.
I've been developing software for more than 20 years but my experience with Android is only 10 months and I've not dived into the big sea of custom ROMs and kernels yet.
My question is simple. How much of custom ROMs and kernels on this device (or any other Android phone) are open source and is it "much" enough to be sure that there is no back door or hidden function?
I would be grateful if ROM and kernel experts can answer this question.
well, honestly this Q sounds a bit strange, but here we go:
1) kernel:
all kernels MUST be 100% open source.
2) device tree
also the device tree has to be open source, just like the kernels
3) ROM
ROMs do not have to be open source. but nearly all (except stock based) custom ROMs for our device are open sourced. otherwise we wouldn't be able to compile them
a special topic are stock ROMs.... i have never seen an open sourced stock ROM from any manufacturer (except google ofc).
now, back doors:
i never heard of a rumor that custom ROMs would have back doors. actually we are working on finding unknown (unwanted) backdoors to fix them.
But for stock ROMs, i personally wouldn't be too sure there is no back door...
Backdoor or not, big agencies (like the NSA for example) do not need backdoors to your phone, they have way more capabilities/possibilities
So it's quite useless thinking about it IMO, as you cannot change anything about it
postacik said:
My question is simple. How much of custom ROMs and kernels on this device (or any other Android phone) are open source and is it "much" enough to be sure that there is no back door or hidden function?
Click to expand...
Click to collapse
Short answer: Not enough.
Longer answer: The kernel and some custom ROMS are open source, but many of the drivers (which operate at root level) remain closed. It should also be plausible to hard-code additional functionality into the hardware of a phone.
The thing that gets the least scrutiny is baseband since it runs on custom hardware. Even with closed source drivers it's arm code running on Linux so lots of people can understand it.
ROMs and kernels aren't really an issue though.