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
I want to use ANT+ with some newer rom and not with the original SonyEricson version, but so far i couldn't fine any.
Latest try was the: MiniCM9-3.0.0 [1/4/12]ICS 4.0.4/CM9 port for the Χ8 by nobodyAtall with his ICS nAa kernel.
It looked promissing, because I could download the ANT Radio Services from Play Store, but as soon as i start an ANT+ enabled program I get messages like:
(ANT+ Demo)
Enabling ANT...
Enable ANT ->
(ANT+ Bike display Demo)
ANT radio not enabled
So it looks like it claims radio is there and functioning, but it doesn't work.
Any thoughts? Otherwise I'll have to go back (again, tried couple times already with different version) to old SE rom.
(The MiniCM9-3.0.0 looks great although battery drain is awful.)
Just as a general statement that applies to every ROM that's being developed from source ...
- Developers can't fix things where the required hardware for testing is missing.
- Developers won't fix things they don't use at all.
In short: Custom ROMs are being made by privateers in their spare-time. None of us is a employee of some smartphone manufacturer having access to tons of testing equipment or having someone to pay the bill for buying crap to conducts tests with.
On topic: Up till today the people I saw posting about ANT+ can be counted easily by just using the fingers of one hand ... so it's safe to assume that none of us actually owns a ANT+ gadget or makes use of it.
Just to make sure, i'm only asking for information.
About your statements:
Developers can't fix things where the required hardware for testing is missing:
The ANT+ radio is available in most Sony Ericson phones, you just need to install the drivers, and the demo programs.
You don't need to buy a heart rate monitor to see if it works.
In the case of the roms i tried, they either didn´t recognise ANT+ or the driver didn't initialize correctly.
Developers won't fix things they don't use at all:
No problem, I'll try to look into it myself.
On topic: ANT+ is one of the coolest things Sony Ericson implemented in their mobile phones.
At least for anyone that has a (Garmin) heart rate monitor with ANT+.
With your phone and ANT+ heart rate monitor you have a cheaper more flexible GPS/heart rate monitor device than you can buy from any company's and can make phone calls.
Ant+ Rom
I haven't verified that it is working, but MiniCM7 claims to have working Ant+. Unfortunately, I can't use it because it requires the nAa Kernel and I can't unlock my bootloader because my phone is the 11W29 model.
If I find a way to safely unlock the bootloader I'll definitely be giving MiniCM7 a try. Other than lacking the ANT+, I'm really happy GingerDX.
If you find any way to get it working, please post the info.
hi guys,
have you managed to get ANT working on any rom? I'm trying to use it on a ray with iced bean 3.0, but it's just saying enabling ant and after a while switches to enable ant. I mention, I have installed the ant radio service ant ant demo from play. an tried to activate with the demo.
thanks.
Dear XDA HTC Desire C Users,
Let me start off by saying I know that this question has been asked before. I've lurked these forums since 2010, I've flashed many devices with many custom roms and kernels. I just want to know what the deal with CyanogenMod is.
I've recently come into possession of a HTC Desire C. It's a great little phone, not what I was expecting at all when I bought it off a bloke at work for £30. Started it up and it was bogged down with all the normal crap you get when someone has a lock stocked phone. Decided to check out XDA once again, and found that there was a port of my favourite rom; CyanogenMod.
I've previously used CM on my Galaxy Europa, Galaxy S 3, Galaxy S4, Nexus 7 and Xperia Play. Using my phone as a WiFi Hotspot/for Wifi Tethering (however you want to say it) was only ever a problem on the Xperia Play (and possibly the Nexus 7, I haven't actually tried). The checkbox would tick, the writing would say "Turning on wireless..." and then that would be it. It would never complete the action. USB tethering has never been an issue, and I never really needed wireless tethering until I got a Nexus 7 around Xmas. Funnily enough, my Xperia Play broke at the same time, and I went back to using the old Europa (CM7, working wifi tether).
Now I've loaded this Desire C up with CM10 with NOPE Kernel v2.6, tried this wifi fix that a lot of people seem to enjoy linking to (granted, it does make WiFi work, but not tethering). Some other suggestions were to use Barnacle WiFi Tethering app, but it creates an ad-hoc connection which a Nexus 7 can't connect to.
I guess it's really a few questions, which I can summarise here for those of you unwilling to read the above text :
- Why does CM have working WiFi hotspot/tether settings on most of my previous devices and not the HTC Desire C?
- Has anyone actually ever got their Desire C to tether with CM10 (any version for the HTC Desire C)? If so, how?
- Are all JellyBean roms having this issue?
- I've read that Sense based ROMs are the only ones that have functional wifi tethering settings. If so, that means I'd have to use an ICS ROM to be able to use wifi tethering?
- Am I doing something wrong? The past few years I've had to relearn how to do all this stuff to a different device each time, I may have missed something that's more prevalent to someone who is immersed in this regularly. My process was as follows -
1) Downloaded CM10 Build 3, TWRP 2.4.2.0, GApps & Nope Kernel v 2.6 (700mhz)
2) Flashed TWRP 2.4.2.0 as recovery (fastboot flash boot recovery.img)
3) Rebooted into Recovery
4) Backed up, wiped & flashed (Factory Reset, Cache, Dalvik, System)
5) Installed CM10 and Gapps (install .zip from sd)
6) Rebooted to Bootloader, flashed NOPE Kernel (fastboot flash boot boot.img)
7) Rebooted to Recovery, wiped Cache/Dalvik Cache
8) Started phone, set up, tried WiFi Tethering.....nothing happened.
As far as I can see, I've probably missed one detail that is affecting the entire process. I assumed that since this was cute_princes v3 marked as "wifi fix", that I wouldn't have to put the folder I linked to earlier onto my phone (the file contatining p2p_supplicant_overlay, wpa_supplicant and wpa_supplicant_overlay).
To confirm, I tried the boot.img that came with CM10, it was some form of Prometheus and that didn't work either. I have tried MiniCM10 as well, same results there. I have flashed NOPE Kernel v2.6 on both CM10 and MiniCM10, to no avail. I also tried the boot.img that was packed with MiniCM10, same result.
Sorry for the long post, but I feel that it's better to over-explain yourself, rather than leaving people guessing. If anyone could shed some light onto this, I'd be very grateful. It's something that made me curious enough to post after 4 years of silence and lurking in the background. The fact that I've managed to root and flash all the previous devices I've owned without ever having to make a post shows that all the information is available to me on this site, and that XDA is such a great place that this information is readily available for me. But in this case, I can't find what I need, so I call to you for help.
Thanks in advance,
Gordon Freeman
It's a cm10 bug.... I don't know if too many people have looked into this....
Sent from my HTC Desire C using XDA Premium 4 mobile app
rudi_j7 said:
It's a cm10 bug.... I don't know if too many people have looked into this....
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's the answer that I hear the most, and I never hear anything more than that. What kind of bug prevents it on certain phones? Why do Sense roms (apparently) have working wifi hotspot?
All my other questions are still open, plus a lot more for discussion. I am only a couple of months away from buying a Nexus 5 anyway, but I need this phone to wifi hotspot in the meanwhile.
Sense ROMs have working Wi-Fi hotspot as they are sort of a modified stock ROM....
Sent from my HTC Desire C using XDA Premium 4 mobile app
rudi_j7 said:
Sense ROMs have working Wi-Fi hotspot as they are sort of a modified stock ROM....
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So you're saying that I have to use an Ice Cream Sandwich ROM if I want to be able to use wireless hotspot/tethering? I'm assuming that if there are no JellyBean ROMs that have working wifi tethering/hotspot, then it has something to do with the phones hardware being unable to work with a newer Android OS. But I'm pretty sure I've read people having success with tethering on JB ROMs.
Maybe someone could point me in the direction of having CM10/any JB ROM with working wifi hotspot/tethering, I'd be grateful.
THIS has been such a deal-breaker for me with the CM10 ROMs. But... Fear not!
The recent MiniCM10 by warrior1208 has fully functional USB and WiFi hotspot tethering! Yippeee! Definitely give the guy/girl credit.
beanaroo said:
THIS has been such a deal-breaker for me with the CM10 ROMs. But... Fear not!
The recent MiniCM10 by warrior1208 has fully functional USB and WiFi hotspot tethering! Yippeee! Definitely give the guy/girl credit.
Click to expand...
Click to collapse
Are you sure that wireless tether is working in Mini CM10? I've flashed this ROM with the provided boot .img and Nope 2.6, and tether did not work. I'm pretty sure I applied that Wifi Fix as well, and nothing seemed to work for me.
Is anyone using a Jellybean ROM with tethering working? I just need to replicate as many possible working combinations of ROM and kernels,so any suggestions of combos would be awesome.
I'm posting this message via WiFi Hotspot. MiniCM10 V3, N.O.P.E. v2.6 850Mhz. No wifi fix applied apart from the WiFi keepalive app (Enabled workaround 2, reselect Always On). USB tether works too, as I use it to install Arch Linux before setting up laptop wireless drivers.
I haven't tried V4 yet. I have a Desire C non-NFC.
beanaroo said:
THIS has been such a deal-breaker for me with the CM10 ROMs. But... Fear not!
The recent MiniCM10 by warrior1208 has fully functional USB and WiFi hotspot tethering! Yippeee! Definitely give the guy/girl credit.
Click to expand...
Click to collapse
First of all, I am a boy! xD...
And yes USB tether works for me...but I didn't try wifi hotspot...
If you can post a screenshot on MINICM 10 forum, then it would be great, so that all people having problems with other also roms come to know...
Thanks!
beanaroo said:
I'm posting this message via WiFi Hotspot. MiniCM10 V3, N.O.P.E. v2.6 850Mhz. No wifi fix applied apart from the WiFi keepalive app (Enabled workaround 2, reselect Always On). USB tether works too, as I use it to install Arch Linux before setting up laptop wireless drivers.
I haven't tried V4 yet. I have a Desire C non-NFC.
Click to expand...
Click to collapse
Thank you for your contribution to the thread. I only have the latest MiniCM10 (V4), but I am also using Nope 2.6, just a lower frequency (700mhz, i have no need for a large OC). I've just clean flashed it back onto my Desire C, and the same results as before. Here are a few screenshots, sometimes screenshots help :
Kernel Version
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ROM Version
WiFi Working (Worked after turning it on then rebooted phone. WiFi was on once rebooted)
Wireless Tether NOT Working
On the last picture, if I back out into the previous menu then re-select to go back into the tethering sub-menu, the "Turning on WiFi..." message disappears and the checkbox is ticked, yet there is still no hotspot being produced.
So I must be doing something wrong still?
EDIT : So I've just flashed on the same kernel and CMMini version as you've said has worked for you. I've installed the "WiFi KeepAlive" app, but I am yet to launch it, as the description of the app (which is very vague) does not seem to mend the ailment that I am having.
I'm providing screenshots of the latest and current installation on my phone. I am not sure if anything in these is out of the ordinary, but maybe someone can tell me if I've done something wrong by looking at my "About Phone" section. Once again, I've provided screenshots of the wifi tether not turning on correctly :
About Phone 1 (Kernel and Baseband Version)
About Phone 2 (CM Version, Build Date and Build Number)
WiFi Tether (Unresponsive, stuck on screen until pressing Back)
WiFi Tether (Shows after exiting and entering again, produces no hotspot visible to other devices)
Working WiFi (After switching on then rebooting, wifi becomes available, but no hotspot)
So if anyone has anything to add, I'd be grateful once more.
Thanks
So after messing around for a while, I've managed to make a slight amount of progress. I feel like I'm almost there now.
I renamed my hotspot "testet" (meant to type "tested", never changed it) and set up WiFi KeepAlive. Using Workaround 2 and Always Keep Wifi On, I managed to get my Nexus 7 to see the hotspot. That's as far as I got, as trying to connect breeds a varying set of results. Whilst it can see the hotspot, it can never fully authenticate. It will hover on "Obtaining IP Address..." and "Authenticating..." before giving me "Saved, secured with WPA2" but not actually connecting to the Internet, or it will say "Avoided poor Internet connection" (or something to that effect). It's frustrating being so close, yet so far. Here are some more screenshots to demonstrate my finds :
Nexus 7 Wifi Screenshots (Various)
The "Turning on Wifi" thing disappeared on my phone and gave me a solid checkbox ticked for once, without having to back out then back in to the menu
See the edit to my previous post to get up to speed on where I am with kernels/ROMs installed.
Thanks again.
So I guess that no one really has any clue about this? Out of the +1,000 views of this thread, only a couple of people could actually contribute?
@warrior1208 , you ported this version of CyanogenMod, and you seemed to think that wifi tether works. Maybe you could shed some light on what I might be doing wrong? I won't have answers such as "It's a known bug", you've pulled the ROM apart and put it back together again, surely you must have some idea about what's going on? I will try to help as much as I can.
@beanaroo have you seen my responses? I have replicated the same setup as you, and had no success at getting this to work. Since you have confirmed that it works, maybe you could give me some advice on what I may be doing wrong?
Failing that, recommend me a JellyBean ROM for this troublesome little phone that has wireless tethering working. I know the common response would be "look through them yourself", but obviously some ROMs claim to have working wifi tether and they do not seem to work when I try them, so if I could get a recommendation then I wouldn't have to trawl through all the "broken" ones and find one that actually works.
No offence to anyones ROMs, it's just that wifi tether is paramount in my use of a phone, and I really wouldn't like to go back to the childish looking ICS ROMs. I don't want to discard this phone either, it's a nifty little thing and I'm quite fond of it.
Thanks again,
Gordon Freeman
Gordon Freeman said:
So I guess that no one really has any clue about this? Out of the +1,000 views of this thread, only a couple of people could actually contribute?
@warrior1208 , you ported this version of CyanogenMod, and you seemed to think that wifi tether works. Maybe you could shed some light on what I might be doing wrong? I won't have answers such as "It's a known bug", you've pulled the ROM apart and put it back together again, surely you must have some idea about what's going on? I will try to help as much as I can.
@beanaroo have you seen my responses? I have replicated the same setup as you, and had no success at getting this to work. Since you have confirmed that it works, maybe you could give me some advice on what I may be doing wrong?
Failing that, recommend me a JellyBean ROM for this troublesome little phone that has wireless tethering working. I know the common response would be "look through them yourself", but obviously some ROMs claim to have working wifi tether and they do not seem to work when I try them, so if I could get a recommendation then I wouldn't have to trawl through all the "broken" ones and find one that actually works.
No offence to anyones ROMs, it's just that wifi tether is paramount in my use of a phone, and I really wouldn't like to go back to the childish looking ICS ROMs. I don't want to discard this phone either, it's a nifty little thing and I'm quite fond of it.
Thanks again,
Gordon Freeman
Click to expand...
Click to collapse
USB Tethering works flawlessly on MINICM10, whereas, for a working wifi hotspot(which is a CYANOGENMOD BUG), we would have to correct the wifi hotspot modules in the github source, and then produce a new build...
So, since we are not working for achieving that, we would never get wifi hotspot on aosp cm based roms...
I hope this information may clear up your doubts...
Here is a screenshot to prove that usb tether works in my ROM...
Unless someone makes a new build WiFi hotspot won't work and since most of the developers are now focusing on building cm11, it is highly unlikely that someone will create a cm10 build 4. You could try using Bluetooth hotspot as an alternative maybe?
Sent from my HTC Desire C using XDA Premium 4 mobile app
rudi_j7 said:
Unless someone makes a new build WiFi hotspot won't work and since most of the developers are now focusing on building cm11, it is highly unlikely that someone will create a cm10 build 4. You could try using Bluetooth hotspot as an alternative maybe?
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have been using Bluetooth tethering, but it's far from what I require. It's quite slow, and Bluetooth drains battery pretty quick. The range is also very limited. Fair enough, I keep hearing the same "it's a known bug in CM10", so what about JB ROMs that aren't made from CM10?
warrior1208 said:
USB Tethering works flawlessly on MINICM10, whereas, for a working wifi hotspot(which is a CYANOGENMOD BUG), we would have to correct the wifi hotspot modules in the github source, and then produce a new build...
So, since we are not working for achieving that, we would never get wifi hotspot on aosp cm based roms...
I hope this information may clear up your doubts...
Here is a screenshot to prove that usb tether works in my ROM...
Click to expand...
Click to collapse
I'm fully aware that USB Tethering works on your build, if you had read any of my posts you'd realise that I already knew that. There was never a dispute as to whether USB Tethering was working. My problem is that @beanaroo claims that he has WiFi Tethering working with your ROM, and you seemed to acknowledge the fact that he had it working. So how can one user make something work that you (the builder of this ROM) claim doesn't work? Unless he is lying, then it must work?
So, other JB ROM alternatives to CM10 then?
EDIT : @warrior1208 I just noticed that your screenshot of your phone shows that Portable WiFi Hotspot is ticked. I know you can select it, go back in the menu and then go forwards again and it remains a solid tick, but why would you include that if you just admitted that it doesn't work? Strange.
Since the only source built jb ROM is cm10, all other ROMs are ported using cm10. That's why the bugs of cm10 are there in every ROM. If someone fixes the tethering and makes a patch or something then it would work. But so far no one has really taken it onto themselves to fix the bug..... So maybe if you could do something......
Sent from my HTC Desire C using XDA Premium 4 mobile app
rudi_j7 said:
Since the only source built jb ROM is cm10, all other ROMs are ported using cm10. That's why the bugs of cm10 are there in every ROM. If someone fixes the tethering and makes a patch or something then it would work. But so far no one has really taken it onto themselves to fix the bug..... So maybe if you could do something......
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Point me in the direction of a ROM building tutorial and I'll happily try my hardest to get it working. I'm not a pro in this kind of thing, but I've been using computers for a couple of decades now so I'm sure I could give it a try. Plus it gives me a reason to get into Android development, as I love Android. I'm totally willing to put some effort into fixing this issue, even if it's just for me. If you could give me pointers on where to look, then I'll give it a shot, although if the CM guys can't do it then I really doubt I'll have a chance.
After all of this, I'm guessing that @beanaroo was lying about his ability to wifi tether on this ROM then?
Gordon Freeman said:
I have been using Bluetooth tethering, but it's far from what I require. It's quite slow, and Bluetooth drains battery pretty quick. The range is also very limited. Fair enough, I keep hearing the same "it's a known bug in CM10", so what about JB ROMs that aren't made from CM10?
I'm fully aware that USB Tethering works on your build, if you had read any of my posts you'd realise that I already knew that. There was never a dispute as to whether USB Tethering was working. My problem is that @beanaroo claims that he has WiFi Tethering working with your ROM, and you seemed to acknowledge the fact that he had it working. So how can one user make something work that you (the builder of this ROM) claim doesn't work? Unless he is lying, then it must work?
So, other JB ROM alternatives to CM10 then?
EDIT : @warrior1208 I just noticed that your screenshot of your phone shows that Portable WiFi Hotspot is ticked. I know you can select it, go back in the menu and then go forwards again and it remains a solid tick, but why would you include that if you just admitted that it doesn't work? Strange.
Click to expand...
Click to collapse
I never mentioned that wifi hotspot works in my ROM...You may ask @beanaroo how he got that working...and yes I was trying in my screenshot to make hotspot stable...But it won't work in any of the Jelly Bean ROMs...So if you want it, you may revert back to a sense ROM as, the sense roms are based on stock rom and hence have everything working...Whereas, all the JB roms for our device have been ported taking cm 10 build 3 as base...I hope this clears up your doubt that YOU CANNOT USE WIFI HOTSPOT ON ANY JELLY BEAN ROM, REVERT BACK TO STOCK OR SENSE BASED ROMS FOR ACHIEVING THAT
You can Google up a 'how to build a ROM from source guide' there are plenty of good ones.
Sent from my HTC Desire C using XDA Premium 4 mobile app
Well I've started looking into some guides now, and once I've installed Ubuntu I'll see what I can do. I think I made some progress, I managed to get the phone to broadcast a signal, there was just a problem with authenticating when connecting. I think once I manage to work out what that problem was, I could make a bit of progress.
In the mean time, I've downloaded a few Sense ROMs which I'll be flashing on to the Desire C until I buy my Nexus 5 next week, which means I'll have the Desire C available for multiple flashes and messing around without having to put my phone out of action for a long time.
Anyway, thanks for the (limited) help. I realised about halfway through that no one really cares enough to try and make it work, I thought people would be up for a crack at this. The lack of enthusiasm was probably down to people not fully reading my posts and checking out all the info I provided, but that's fine. If I get anywhere, I'll let you know.
I read that the Pixel 4 and 4 XL have DisplayPort Alt Mode disabled on the Kernel and was wondering if anyone has made or started working on a custom Kernel that enables this feature? Is it even possible? Yeah I know I can use Chromecast or cast via WiFi but nothing beats a direct HDMI connection due to virtually no input lag etc.
Thanks.
marsfan89 said:
I read that the Pixel 4 and 4 XL have DisplayPort Alt Mode disabled on the Kernel and was wondering if anyone has made or started working on a custom Kernel that enables this feature? Is it even possible? Yeah I know I can use Chromecast or cast via WiFi but nothing beats a direct HDMI connection due to virtually no input lag etc. Thanks.
Click to expand...
Click to collapse
Based on no replies in over 65 views I would say no, but you may have better luck posting this over in the Kernels section. That, and maybe linking to the piece you found on this disabled feature waiting to be unlocked.
Still no progress on this? This would be the only reason for me to root.
shagggggggy said:
Still no progress on this? This would be the only reason for me to root.
Click to expand...
Click to collapse
No, unfortunately its still not possible. It is 100% hardware capable and only blocked at the Kernel level unlike Pixel 1-3. It's entirely possible to one day have it enabled but right now it doesn't seem to be a priority for any of the great Kernel devs we have here which is completely understandable. Although there are a bunch of us that would love to have this feature, its still a niche feature and so devs priorities are focused on the broader features for us. I read that Google MAY activate the display out over usb when stadia launched as that would make a lot of sense to tout as a feature but that hasn't happened yet and I'm not holding my breath.
Honestly, I'd be ecstatic just to have display out over WiFi (Miracast) enabled and there is a magisk module that enabled it on Pie for the Pixel 2-3, I loved having that when I was still on my Pixel 2 XL.
1dopewrx05 said:
No, unfortunately its still not possible. It is 100% hardware capable and only blocked at the Kernel level unlike Pixel 1-3. It's entirely possible to one day have it enabled but right now it doesn't seem to be a priority for any of the great Kernel devs we have here which is completely understandable. Although there are a bunch of us that would love to have this feature, its still a niche feature and so devs priorities are focused on the broader features for us. I read that Google MAY activate the display out over usb when stadia launched as that would make a lot of sense to tout as a feature but that hasn't happened yet and I'm not holding my breath.
Honestly, I'd be ecstatic just to have display out over WiFi (Miracast) enabled and there is a magisk module that enabled it on Pie for the Pixel 2-3, I loved having that when I was still on my Pixel 2 XL.
Click to expand...
Click to collapse
Where did you get the information that the pixel 4 xl (I have only tried it on the XL model since I don’t own the regular one) is actually capable of this?
I have seen none other source of information than the google commits disabling it in the kernel.
I enabled it at kernel level and all I got was a freeze when the phone booted.
Freak07 said:
Where did you get the information that the pixel 4 xl (I have only tried it on the XL model since I don’t own the regular one) is actually capable of this?
I have seen none other source of information than the google commits disabling it in the kernel.
I enabled it at kernel level and all I got was a freeze when the phone booted.
Click to expand...
Click to collapse
I've read it from multiple sources. I was seeing it quite a bit shortly after the phone was released and haven't seen anything about it recently but I've found an article for you showing the information I was talking about:
Via AndroidPolice:
"A commit has been found in the Android source code that disables DisplayPort over the USB Type-C port in the Pixel 4. The commit message simply reads, "Disable DP function."
The link to the whole article is:
"Pixel 4 has USB video output disabled in software" https://www.androidpolice.com/2019/11/03/pixel-4-has-usb-video-output-disabled-in-software/?amp
It's possible Google never finished it implementing the feature or maybe it didn't work fully before they had to release the phone. Is there any chance you want to PM me a copy of your kernel with it enabled? I have a couple of ideas on trying to get it fully enabled and working semi-reliably.
1dopewrx05 said:
I've read it from multiple sources. I was seeing it quite a bit shortly after the phone was released and haven't seen anything about it recently but I've found an article for you showing the information I was talking about:
Via AndroidPolice:
"A commit has been found in the Android source code that disables DisplayPort over the USB Type-C port in the Pixel 4. The commit message simply reads, "Disable DP function."
The link to the whole article is:
"Pixel 4 has USB video output disabled in software" https://www.androidpolice.com/2019/11/03/pixel-4-has-usb-video-output-disabled-in-software/?amp
It's possible Google never finished it implementing the feature or maybe it didn't work fully before they had to release the phone. Is there any chance you want to PM me a copy of your kernel with it enabled? I have a couple of ideas on trying to get it fully enabled and working semi-reliably.
Click to expand...
Click to collapse
Yes all these articles base back to the commit that actually disables the function in the display driver. There´s no source of information that the Pixel 4 XL is actually capable of doing it. I think that´s why they disabled it.
So I don´t understand why you think the phone is 100% hardware capable of doing this, if you have no other information.
The phone freezes before the bootanimation comes up when the commit is reverted. So I´m not sure what you want to do that doesn´t involve recompiling the kernel with additional changes of your own.
I´d need to recompile the kernel as I did this already last year and the kernel is by now incompatible with the current firmware.
Freak07 said:
Yes all these articles base back to the commit that actually disables the function in the display driver. There´s no source of information that the Pixel 4 XL is actually capable of doing it. I think that´s why they disabled it.
So I don´t understand why you think the phone is 100% hardware capable of doing this, if you have no other information.
The phone freezes before the bootanimation comes up when the commit is reverted. So I´m not sure what you want to do that doesn´t involve recompiling the kernel with additional changes of your own.
I´d need to recompile the kernel as I did this already last year and the kernel is by now incompatible with the current firmware.
Click to expand...
Click to collapse
Yeah that wasn't the actual source I heard that from, like I said this was coming up on a year ago so I'll likely never find the sources.
Look, I mean you're most likely right about it not being a possibility, I know you have more knowledge of this stuff than I do so I'll take your word. I gave up on this a long time ago I was just replying to the OP with what I remembered. I have Chromecasts on my house TV's so it's not even relevant to me anymore.
What's your view on enabling display-out over WiFi? Outside of a Chromecast I mean. There was a magisk module for the Pixel 2 on Pie that re-enabled the Miracast support that Google disabled.