Related
** I'd like if this thread was kept to ONLY contributing to the solution to the known issues, no asking for eta's feature requests in other ROM's **
Its been confirmed that the Audio issue is in the AudioLib's. So far numerous people have been swapping out libaudio's from different device trees has different results. Bluetooth hasn't been targeted yet - I personally believe that the hands free phone over bluetooth is connected to the libaudio.
************************************** EDIT *************************************
http://e2e.ti.com/support/embedded/android/f/509/p/198799/790457.aspx as found and posted here by lorddavid
The above link has some great insight to what the issue is, it talks about it being the sampling rate of the microphone and the speaker (input and output) being differnt. This is why the playback would change to slow motion .. It makes perfect sense! .. The only question now is how do we implement this into our ROMs to fix it ... I'm guessing there's an audio driver that needs to be modified from the source .. I haven't looked at the source code yet myself but following what was posted above into any of our roms with the audio issue may resolve.
Logcat confirms this :
Exxon02 said:
I can't post in the developer forums, but I have some input on the slow audio issues. I noticed the problem happening with Skype and the new TeamSpeak 3.0 beta, so I scanned for errors in the logcat when starting them. Both programs showed the same error.
E/AudioRecord( 6545): Unsupported configuration: sampleRate 48000, format 1, channelMask 0x1
Click to expand...
Click to collapse
So it appears our issue may be related to the sample rate as previously suggested.
Click to expand...
Click to collapse
********************************* UPDATE - AUDIO **************************
If you would like to test this patch by Adam77Root do a Nandroid backup first. It will get Skype working, however, it will start to use the back loudspeaker (think playing MP3's) for the regular cellular voice calls and for skype. The audio sampling rate is fixed in this patch but you'll be stuck with speakerphone type calls.
Adam77Root said:
Here comes the Skype fix! This also solves using microphone and speaker parallelly. The fix is actually using the stock libaudio from Galaxy Tab 10.1 and adding the necessary modifications to libmedia and libaudioflinger. Voice calls work fine.
Note: These libs have the Samsung audio bug! Sometimes volume settings are a bit weird, even though I have enabled the patch. Be aware of this.
Link: http://www.mediafire.com/?49u6ua55kbr1j6b
Click to expand...
Click to collapse
***************** UPDATE - BLUETOOTH *********************
tonyp said:
bubor contacted me via PM asking about the bluedroid -> bluez port which I recently did for my CM10.1 LG Optimus 2x ROM (Tegra2 as well).
I will answer it here publically to help as many devs on your phone as possible
I had been in contact with Andrei Emeltchenko who managed to properly port bluez for his company.
After my mail he kindly asked for permission to release the sources and published it completely at: http://gitorious.org/android-bluez
You can fork most repos from my Github profile - there's everything except frameworks/base and packages/apps/Settings, which aren't published.
With bluez bluetooth should work exactly the same as on Android 4.1!
Hope this information will help you to get bluetooth rocking on your device as well :good: :highfive:
Edit: of course you need to adapt your device tree to bluez as well.
Here's the commit where I did it for my device:
https://github.com/tonypp/android_d...mmit/b767cdbef5e262daf01d3bb38b13ab01d2cbc18a
You just need to restore the CM10 bluetooth stuff and add the bluetooth packages to the makefile.
Click to expand...
Click to collapse
For bluetooth theres fixes in different forums because bluetooth has been a big problem for other devices with 4.2.2. Even the nexus 7 was having problems on custom roms.
Sent from my SAMSUNG-SGH-I727 using xda premium
spitfire2425 said:
For bluetooth theres fixes in different forums because bluetooth has been a big problem for other devices with 4.2.2. Even the nexus 7 was having problems on custom roms.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I guess a linux box needs to be setup to compile a new kernel... thegreatergood left a link to the sources somewhere, this I recall... What other device are similar to ours in terms of chipset etc? ... S2 ?
yohan4ws said:
I guess a linux box needs to be setup to compile a new kernel... thegreatergood left a link to the sources somewhere, this I recall... What other device are similar to ours in terms of chipset etc? ... S2 ?
Click to expand...
Click to collapse
Again, no, the S2 has Exynos while our phone has Tegra 2, if you're looking for the device that resembles the most of the glides specs, the Galaxy R it's the closest one I think
Maybe is ther any possibilitie to ask for some help in the galaxy r forum? maybe someone can give a look to our roms or give us some hints
Source code for our kernel comes from google AOSP + the code supplied by Samsung here:
http://opensource.samsung.com/ (search for i927)
Samsung has only released ICS code and this is what has been applied against the JB source tree. If that's right or not I have no idea...
As for the sources for the kernels they are all in The-Covenant's github:
https://github.com/The-Covenant
The LiteKernel---Glide repository is thegreatergood's code and android_kernel_samsung_i927 is the source for The-Covenant's kernel.
I have built the LiteKernel source and have the environment setup here. I've just been concentrating on getting the ROM side of things down first. That's coming along well so if you guys can get some insight as to what needs to be changed in the kernel source I'm more than willing to give it a go.
I do own a glide so quick tests are really easy...
what about taking a look on the soruce for the kernel/rom form the offical cm10.1 for the i9103 who has the same tegra 2 chip?
yohan4ws said:
Its been confirmed that it's in the Kernel, so my question is are we missing a driver for the chipset in our phones ? (Broadcom something..)
Click to expand...
Click to collapse
Thanks for making this thread yohan.
I'm not convinced it's a kernel issue though. Maybe a first step would be to get logcats and dmesg from a working ICS system and a non-working CM10.1 or similar system? IMHO important points would be logs during boot, during HSP pairing, and during call initiation.
I can take doing the ICS logs this weekend (wife's phone is on ICS), if somebody can do the equivalent with JB.
Spyke can you point me in the direction of how to setup the build environment for the kernel source ? First thing I'm going to do is follow dmans how to compile and dl thee kernel sources thx for that info and the above.. I can post logcats and dmesg no problem from both...
Has anyone tried the Bluetooth fix for other devices?
Sent from my SGH-i927 using xda premium
yohan4ws said:
Spyke can you point me in the direction of how to setup the build environment for the kernel source ? First thing I'm going to do is follow dmans how to compile and dl thee kernel sources thx for that info and the above.. I can post logcats and dmesg no problem from both...
Click to expand...
Click to collapse
Which kernel you looking to build?
There are two source trees you can start from:
https://github.com/The-Covenant/LiteKernel---Glide/
or
https://github.com/The-Covenant/android_kernel_samsung_i927
I've figured out the Lite-Kernel so far. You follow dman's guide up to the point of the source downloads. Here you just need the kernel source, nothing else. Once that's done you also want to install Linaro for your distro, and then adjust the Build4.X/Build KERNEL.sh files with the path to your Linaro install. After that just go into the correct Build folder and run the Build KERNEL.sh file and you should end up with a flashable kernel.
I've not done The-Covenant kernel at all yet so can't comment there.
I have also done a AOSP + Samsung sources build for ICS in the past, so that may be a good place to start so you can compare the working sources to the other two trees.
Let me know if you need more details and I'll guide you through it.
sorry to bother, but which custom roms does have BT headset working? thx!
spyke555 said:
Which kernel you looking to build?
There are two source trees you can start from:
https://github.com/The-Covenant/LiteKernel---Glide/
or
https://github.com/The-Covenant/android_kernel_samsung_i927
I've not done The-Covenant kernel at all yet so can't comment there.
Click to expand...
Click to collapse
I have The-Covenant kernel running (and a current CM 10.1 userland), but I'm having general audio input issues. Was going to debug the Bluetooth stuff, but running anything requiring audio input hangs.
Logcat shows "AudioHardware: cannot open pcm_in driver: cannot set hw params: Invalid argument". Not very descriptive.
This seems kind of ALSA related. Do you see this with your LiteKernel builds?
I search a little about that error, and found this
http://e2e.ti.com/support/embedded/android/f/509/p/198799/790457.aspx
http://forum.xda-developers.com/showthread.php?t=1748873
Maybe help a little. Do you think that all the audio issue (bluetooth, skype, sound recorder, etc) is for the same problem?
lorddavid said:
I search a little about that error, and found this
http://e2e.ti.com/support/embedded/android/f/509/p/198799/790457.aspx
Maybe help a little. Do you think that all the audio issue (bluetooth, skype, sound recorder, etc) is for the same problem?
Click to expand...
Click to collapse
Great search, I'm willing to bet that this is the issue right here - audio sampling rate different between input and output. Everything makes sense.
Just have to dig in further now and compare source codes... anyone have the setup and feel like taking a stab at it ? I haven't had a chance to setup an ubuntu VM yet.
epsalmond PM'd me this info ...
epsalmond said:
Hi,
I saw your brainstorming post in the cap glide forum.
I can't post in Dev forums yet (damn noobs ruin everything) but I didn't see the info there so I'm sending a pm.
I have read in multiple places that google has dropped support for systems without NEON instructions
This includes tegra2.
I had the idea to merge kernel from the galaxy r which is basically our phone without a keyboard and diff the audio API to see what's changed. I know jb does have some new audio API's that have caused minor problems with some apps.
I'm travelling in south America so I've had trouble syncing all the sources I need for this, but I should have something in a week or so.
If you can update the thread with this so we have it in the cap glide forum maybe someone else can contribute as well.
Click to expand...
Click to collapse
yohan4ws said:
epsalmond PM'd me this info ...
Click to expand...
Click to collapse
So, that means all the issues may be related ? BT, Audio Recording with default Camera App and Skype/Anyothervoipapp ? If epsalmond it's right, that will mean that we only need to find one solution to solve all the problems, and then boom ! Fully functional JB on the Glide, that means that anybody with the knowledge to compile a ROM will be able to take all the "Unsupported" ROM's like PAC, PA, LS, SL, Vanilla RootBox, and incorporate the "FIX" on them, damn, that would be nice
santimaster2000 said:
So, that means all the issues may be related ? BT, Audio Recording with default Camera App and Skype/Anyothervoipapp ? If epsalmond it's right, that will mean that we only need to find one solution to solve all the problems, and then boom ! Fully functional JB on the Glide, that means that anybody with the knowledge to compile a ROM will be able to take all the "Unsupported" ROM's like PAC, PA, LS, SL, Vanilla RootBox, and incorporate the "FIX" on them, damn, that would be nice
Click to expand...
Click to collapse
I believe so, think about it .... The audio only slows down when the microphone is enabled ... Video Camera .. Skype ... Bluetooth .
Because its a sound issue, it also means its a kernel issue (corrected me if I'm wrong) ... so an updated Kernel will resolve the issues across all ROMs should this be correct.
I have built up an Ubuntu box now and a build environment... I have no frikin idea what I'm doing but I know that I need to find the source for the audio driver ... I believe I found it here :: https://github.com/CyanogenMod/android_device_samsung_i927/tree/jellybean/libaudio
I think that there is a variable set somewhere to the sampling rate and there will be multiple area's that need to be looked at in order to fix the input sampling rate.
Once this is fixed, the only real things left are Torch from the toggles ....picture orientation, and that some apps disappear on reboot unless they're "moved to SD"... and battery too, I guess...
other kernel
Hello,
Build kernel from https://github.com/CyanogenMod/android_kernel_samsung_n1 with our config, but still broken bt audio.
Installed official cm10.1 and PACman 20.1.0 build for galaxy r with litekernel, but broken bt audio too.
bubor said:
Hello,
Build kernel from https://github.com/CyanogenMod/android_kernel_samsung_n1 with our config, but still broken bt audio.
Click to expand...
Click to collapse
Maybe is not only kernel. Adam say in his thread, that he thinks that know what can be the issue, but never say anything more :/
This is an experimental build of CyanogenMod 10.1 for Asus TF300T and TF300TG with the new bootloader 4.2.
If you are an experienced CyanogenMod user, please give it a try and let me know anything I broke.
But please see "Known Issues" below.
Would also be interesting to hear about results on different boot loaders.
Note that this is an unofficial build.
I will provide updates, as things are being fixed, but I don't plan to provide regular nightlies.
Instead I hope that my changes will be merged by CM, once all is working as expected.
Supported Bootloaders
Installed by Asus ROM v10.6.1.15.3 (aka bootloader 4.2).
Should also work with v10.6.1.8 (aka bootloader 4.2).
The current download does not work on the old JB 4.1 bootloader installed with Asus ROM v10.4.2.20.
Testing or fixing this is currently not a priority; even might not work at all.
Extras
Some extras I included that are not part of the official CM distribution:
My kernel patch to make DriveDroid work. See the app thread for more details:
[APP][2.2+] DriveDroid - host ISO/IMG files to boot your PC from
Known Issues
Camera is crashing since 20130430 version. Sorry!
Audio and YouTube videos play about 9% too fast. MX Player works fine.
[WHEN CAMERA WAS WORKING...] Setting camera to burst 20 pictures will stop after 8-14 on average.
No radio on TF300TG.
Downloads
Get the latest version:
cm-10.1-20130509-EXPERIMENTAL-tf300t.zip - 160.11 MB
Older downloads for comparison:
cm-10.1-20130506-EXPERIMENTAL-tf300t.zip - 160.21 MB
cm-10.1-20130430-EXPERIMENTAL-tf300t.zip - 161.95 MB
cm-10.1-20130428-EXPERIMENTAL-tf300t.zip - 163.58 MB
cm-10.1-20130427-EXPERIMENTAL-tf300t.zip - 163.58 MB
The latest source code is available from branch cm-10.1 in these two repositories:
https://github.com/f69m/android_device_asus_tf300t
https://github.com/f69m/android_kernel_asus_tf300t
For more details, please see "Building from Source" below.
Changes
Coming Soon:
Fix audio, when keyboard dock is connected; unfortunately this removes support for USB audio.
2013-05-09:
WLAN and audio working on TF300TG.
Small fix for camera, but not working yet.
Properly setting Bluetooth MAC address.
2013-05-06:
Bluetooth working fine for me.
WLAN should be stable for everyone now.
libsurfaceflinger is built from source again, the segfault is fixed.
The screen flickering is definitely gone; running really smooth now.
2013-04-30:
Updated all blobs and config files.
Included libsurfaceflinger from Asus to avoid segfault.
Include patch for DriveDroid.
2013-04-28:
Merged Asus kernel v10.6.1.15.3.
ROW scheduler is back and is default.
GPS updated and tested.
Bluetooth working, but can't re-enable once turned off.
2013-04-27:
New kernel based on Asus v10.6.1.8.4.
Some blobs and configs updated.
These are only the changes made by myself and jsfrk specifically for this build.
The latest changes from CyanogenMod are also included, but not explicitly listed.
Instructions
This experimental ROM is targeted at experienced users that can help test and make it work.
If you are new to CyanogenMod and you need instructions on how to use the download, it is not for you yet. Sorry!
Building from Source
Basically you can follow the guide for building CyanogenMod with one exception.
Initialize your CyanogenMod source repository with:
Code:
repo init -u git://github.com/f69m/android -b cm-10.1-tf300t
You can also run this command in an existing repository.
Credits
The whole amazing CyanogenMod team.
jsfrk for testing and fixing issues on TF300TG.
Asus for breaking bootloader compatibility again.
First download is available!
Of course in my "final" build, I had borked WLAN.
So did a "more final" build, which is now available for download.
Just confirming, it does NOT work with the 4.1 bootloader. The boot animation freezes.
Just another reason for me to update my tablet this weekend. I'll be flashing this for real some time today. Thanks.
Update available:
Merged Asus kernel v10.6.1.15.3.
ROW scheduler is back and is default.
GPS updated and tested.
Bluetooth working, but can't re-enable once turned off.
Really awesome rom! very quick and smooth. But the screen keeps flickering.
crazynitro said:
Really awesome rom! very quick and smooth. But the screen keeps flickering.
Click to expand...
Click to collapse
Yes, I noticed that too.
First step is to update the graphics drivers, I hope that will fix it.
Still getting a segfault with the new drivers though.
Thanks for your feedback!
Sent from my TF300T using Tapatalk HD
I'll be following this thread closely, as I am just too lazy to downgrade my bootloader. Do you need any internal testers? I'm available.:good:
*Edit 1* Flashed without Gapps, it's buttery smooth with no issues (besides bluetooth.) Burst mode in camera works unless you set it to 20 shots, then it takes about 8-14 (average) before stopping. The calculator works. Wifi is a little spotty (randomly disabling and re enabling itself.) Random screen flashes,i'm not bothered by it.
*Edit 2* Flashed with Gapps, all of the above true. WiFi needs a lot of work, it unbearably slow on this ROM.
Downtown taco said:
I'll be following this thread closely, as I am just too lazy to downgrade my bootloader. Do you need any internal testers? I'm available.:good:
Click to expand...
Click to collapse
Hmm, not sure, what you mean with "internal tester"? But I am sure happy about everyone giving feedback, thanks!
*Edit 1* Flashed without Gapps, it's buttery smooth with no issues (besides bluetooth.) Burst mode in camera works unless you set it to 20 shots, then it takes about 8-14 (average) before stopping. The calculator works. Wifi is a little spotty (randomly disabling and re enabling itself.) Random screen flashes,i'm not bothered by it.
*Edit 2* Flashed with Gapps, all of the above true. WiFi needs a lot of work, it unbearably slow on this ROM.
Click to expand...
Click to collapse
Have not seen any WLAN disconnects yet, but indeed, the whole WLAN and Bluetooth code needs redoing (same chip, same driver).
When trying to fix Bluetooth, I usually break WLAN completly, without making Bluetooth work properly.
Next update will be mostly blobs and config files. Doing that slowly to figure out, where that segfault is coming from.
After that will restart the WLAN/Bluetooth code from scratch. Well, from the Asus code that is.
Currently using the code from official CM BL4.1 kernel.
New download that has now all blobs and config files updated!
Seems the random screen flickering is gone, please let me know, if you still see it.
Well, being a bad boy, I included libsurfaceflinger from Asus, though this should really be the one compiled from the CM sources.
But for now it avoids a segfault and it seems OK, while we have worse issues with WLAN and Bluetooth.
Also included a little extra patch that has not been merged into the official CM kernel.
It makes DriveDroid work on our beloved TF300T. For more details see the app thread:
[APP][2.2+] DriveDroid - host ISO/IMG files to boot your PC from
Is there a hope for TF300TG support? I've installed 28Apr build on my TG device with 4.2 BL, and it booted just fine, but WiFi wasn't working.
kykc said:
Is there a hope for TF300TG support? I've installed 28Apr build on my TG device with 4.2 BL, and it booted just fine, but WiFi wasn't working.
Click to expand...
Click to collapse
Sorry, I don't have access to a TF300TG, so can't test it.
Of course I am happy to clean up and push out my current sources, if there is a developer who wants to port it to the TG.
Otherwise I'd save the time for cleaning up now and push it out, once I am happy.
Sent from my TF300T using Tapatalk HD
kykc said:
Is there a hope for TF300TG support? I've installed 28Apr build on my TG device with 4.2 BL, and it booted just fine, but WiFi wasn't working.
Click to expand...
Click to collapse
Glad to let you all know that we found a developer owning a TF300TG!
So I did a big cleanup and pushed things out to GitHub. Please see the first post for details.
Also the graphics lib I had replaced is back in; the segfault is fixed.
It is running incredibly smooth now!
But the camera is still broken. :crying:
I'll have another go at the camera issue, before releasing a new update.
f69m said:
Glad to let you all know that we found a developer owning a TF300TG!
So I did a big cleanup and pushed things out to GitHub. Please see the first post for details.
Also the graphics lib I had replaced is back in; the segfault is fixed.
It is running incredibly smooth now!
But the camera is still broken. :crying:
I'll have another go at the camera issue, before releasing a new update.
Click to expand...
Click to collapse
I'll take whatever version is up now for a spin. I expect most to be the same, minus screen flickers. Am I right?
Sent from my Galaxy Nexus using Tapatalk 2
Downtown taco said:
I'll take whatever version is up now for a spin. I expect most to be the same, minus screen flickers. Am I right?
Click to expand...
Click to collapse
Yes, in the 20130430 version the screen flickering is gone and it is running very smooth.
But also the camera is broken, which worked in the previous versions.
The camera is giving me quite a headache...
Sent from my TF300T using Tapatalk HD
f69m said:
Yes, in the 20130430 version the screen flickering is gone and it is running very smooth.
But also the camera is broken, which worked in the previous versions.
The camera is giving me quite a headache...
Sent from my TF300T using Tapatalk HD
Click to expand...
Click to collapse
It's always the camera...
Sent from my Galaxy Nexus using Tapatalk 2
Just tried a quick install of the ROM. gotta say that it is very smooth and it just feels so snappy its nuts! But yeah, the camera force closes
Sent from my ASUS Transformer Pad TF300T
pcoussa said:
Just tried a quick install of the ROM. gotta say that it is very smooth and it just feels so snappy its nuts! But yeah, the camera force closes
Click to expand...
Click to collapse
Thanks!
Yeah, luckily I have a very strong head, so eventually the camera will have to yield.
Temporarily the camera has won though; I put it aside and first looked into WLAN and Bluetooth.
Good news is, here I am hearing music via Bluetooth from my Laptop speakers!
And even after switching off and on.
So I guess there will be an update later today with WLAN more stable and Bluetooth working.
We are also working on WLAN on the TF300TG and have that somewhat working, too!
Though might not be in today's release yet.
Sent from my TF300T using Tapatalk HD
New update available!
Sorry, the camera is still broken... :crying:
BUT... Bluetooth is now working fine for me.
I don't own any real Bluetooth devices though. I tested using my laptop as a Bluetooth audio sink.
Was funny to hear the music and notification sounds come out of the laptop!
Also WLAN should now be stable for everybody.
I changed the kernel code over to the Asus code and more important fixed an issue with loading the WLAN firmware.
The latter might explain the different responses I got: from "not working at all", over "spotty, random disconnects" to "working fine".
Probably your mileage depended on the WLAN firmware installed by your previous ROM.
Well, please let me know, how it works for you now.
Thank you all for your feedback!
f69m said:
New update available!
Sorry, the camera is still broken... :crying:
BUT... Bluetooth is now working fine for me.
I don't own any real Bluetooth devices though. I tested using my laptop as a Bluetooth audio sink.
Was funny to hear the music and notification sounds come out of the laptop!
Also WLAN should now be stable for everybody.
I changed the kernel code over to the Asus code and more important fixed an issue with loading the WLAN firmware.
The latter might explain the different responses I got: from "not working at all", over "spotty, random disconnects" to "working fine".
Probably your mileage depended on the WLAN firmware installed by your previous ROM.
Well, please let me know, how it works for you now.
Thank you all for your feedback!
Click to expand...
Click to collapse
I'll give it a run later tonight
Sent from my Galaxy Nexus using Tapatalk 2
Hmm, 10 downloads and no one speaking up so far...
I take that as a good sign!
More good news: we got WLAN working on TF300TG too.
There are still issues with sound though.
Is there any developer with a TF300TL around? Would be great to cover the lot!
Currently updating my Ubuntu Touch port to the new code for BL 4.2.
Apart from getting some work done on UT, I hope that using Ubuntu, I might gain another view on the camera issue.
It's so frustrating: everything between the Android camera HAL and the kernel is a black box. No documentation and no source code.
Just some error messages in logcat and some in dmesg... but why?
Sent from my TF300T using Tapatalk HD
You might already know about the existence of the beautiful SailfishOS, what if it was possible to port it to our XPERIAS? It would look great on XS! Waiting for suggestions.
Wtf, QT based? MeeGo based? Last time I heard these words was when I was on symbian .
Personally I don't like the UI, and the android app compatibility
Sent from my LT26i using xda app-developers app
Ahh c'mon dont be that agressive! It's just and experiment, Sailfish is open source and can be ported, it only depends on the devs, will they do it or not.
MY BAD!!!
I messed up the pages and posted my thread into wrong section!!! Please remove it, I wanted to post it in the Q&A.
Sorry Sorry Sorry....
Oooohhh yeah, I really love Meego and Sailfish would be one very nice addition to ever growing Xperia S ROM collection
Would love Dual-Boot it on my Xperia S
Hope some friendly dev port it to our Xperia S.
Would love to have this wonderful OS. This is what Nokia essentially could've had instead of that other OS. It looks very well designed and very thoughtfully done.
https://www.youtube.com/watch?v=zxv7iXwIgno
If we can't get it ported, I'd at least love the launcher xD
Sent from my LT26i using xda premium
Would love to have this wonderful OS.
please can we have this
bclub said:
please can we have this
Click to expand...
Click to collapse
i dont think we ever get this bcoz we have only left 1 or two active developers for our xperia s.where other devices have plenty of roms, we just have one rom to play....Thanks to mickybart who is still making Xperia s alive....
In fact Sailfish OS is not 100% open source. All the UI is closed source.
Android compatibility is not supported on "custom" ROM too and it is not possible to buy a licence per device for now.
And last financial situation was not so great :/ (I hope that Jolla will survive and will be able to deliver a new phone in the future)
So that make interest more limited to work on it hardly.
I have already attempt to run SailfishOS and all sources to compile it are available under my github (https://github.com/mickybart/). The main issue is about hwcomposer implementation that is not working for our device. After long hours of troubleshooting I was not able to run the graphical stack. I forced clock initialization on the kernel too to avoid issues and it was better (no more kernel panic) but not enough to fix the problem. In fact the issue seems to be on the GPU driver because hwc initialization is done as it is done by SurfaceFlinger but it fails.
I have an experimental solution that permit me to run interface with SurfaceFlinger. So it is supposed to be possible to adapt lipstick (wayland compositor used by mer-hybris/SailfishOS) to use SurfaceFlinger but I chose to work on plasma mobile for now.
mickybart said:
In fact Sailfish OS is not 100% open source. All the UI is closed source.
Android compatibility is not supported on "custom" ROM too and it is not possible to buy a licence per device for now.
And last financial situation was not so great :/ (I hope that Jolla will survive and will be able to deliver a new phone in the future)
So that make interest more limited to work on it hardly.
I have already attempt to run SailfishOS and all sources to compile it are available under my github (https://github.com/mickybart/). The main issue is about hwcomposer implementation that is not working for our device. After long hours of troubleshooting I was not able to run the graphical stack. I forced clock initialization on the kernel too to avoid issues and it was better (no more kernel panic) but not enough to fix the problem. In fact the issue seems to be on the GPU driver because hwc initialization is done as it is done by SurfaceFlinger but it fails.
I have an experimental solution that permit me to run interface with SurfaceFlinger. So it is supposed to be possible to adapt lipstick (wayland compositor used by mer-hybris/SailfishOS) to use SurfaceFlinger but I chose to work on plasma mobile for now.
Click to expand...
Click to collapse
Hello sir...I am a great fan of yours and it worths...I follow your git everyday..I saw you are working on a project named hybris 5.1.1...can you tell me something about it???asking for my curiosity...sorry for my bad English
Sent from my C1904 using XDA-Developers mobile app
mihirtherocks said:
Hello sir...I am a great fan of yours and it worths...I follow your git everyday..I saw you are working on a project named hybris 5.1.1...can you tell me something about it???asking for my curiosity...sorry for my bad English
Sent from my C1904 using XDA-Developers mobile app
Click to expand...
Click to collapse
In fact the project is gnulinux_support (that include hybris with gnulinux-support-5.1 branch). For now I'm testing and writing the documentation to officially release this new project.
I will create an official xda project really soon (this week or next one if everything is good ! Take me longer time than expected !). The state of the project is very good but it will be reserved for developers to start.
You will know more soon
mickybart said:
In fact the project is gnulinux_support (that include hybris with gnulinux-support-5.1 branch). For now I'm testing and writing the documentation to officially release this new project.
I will create an official xda project really soon (this week or next one if everything is good ! Take me longer time than expected !). The state of the project is very good but it will be reserved for developers to start.
You will know more soon
Click to expand...
Click to collapse
Thank u sir for your reply
We already have the ability to boot multiple ROMs and plenty of kernels available. Ubuntu Touch is not being built because it is based off of CM10 (4.2) which flo/deb never ran and as a result are unsupported. However, what is stopping devs from using the kernels available to boot full ARM versions of ubuntu, debian, arch or gentoo? I've looked at the nexus 7 2012 and there has been plenty of such development, even sooner after its release. Is this nexus doomed to solely run android due to the qualcomm processor it possesses?
Also, please note, I'm not looking to run linux INSIDE android (chroot method). That is possible on just about every android device known to mankind and nothing special. I want to run linux as a ROM. This has been previously accomplished on popular tablets like the nexus 7 2012, note 10.1 and the transformer prime, just to name a few.
Bump?
Do you have any links regarding a native linux implementation on the 1st gen Nexus 7? I'd like to look into it, sounds interesting.
I found two separate attempts to bring Linux on this tablet:
wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7 and github.com/Bogdacutu/flo-Fedora
None of them are successful yet - I guess display (or any other debug output method) is a blocker here. AFAIK Tassadar has managed to make an UART cable - delta.fratler.de/68-raiders-lost-uart/
Managed to run Bogdancutu's flo-Fedora (updated to F20 though), but I cannot get the screen to work. Any ideas/tips?
vrutkovs said:
I found two separate attempts to bring Linux on this tablet:
wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7 and github.com/Bogdacutu/flo-Fedora
None of them are successful yet - I guess display (or any other debug output method) is a blocker here. AFAIK Tassadar has managed to make an UART cable - delta.fratler.de/68-raiders-lost-uart/
Click to expand...
Click to collapse
The first is for the original nexus 7, seeing how it is Tegra3.
vrutkovs said:
Managed to run Bogdancutu's flo-Fedora (updated to F20 though), but I cannot get the screen to work. Any ideas/tips?
Click to expand...
Click to collapse
Mind posting a link? I can't find the thread on xda.
NVM: https://github.com/Bogdacutu/flo-Fedora
Still chroot, not exactly native, but the screen is run through X11 as opposed to a vnc server. Pretty good actually.
Here's Ubuntu on the 1st gen Nexus 7:https://wiki.ubuntu.com/Nexus7/Installation
x10knight said:
Here's Ubuntu on the 1st gen Nexus 7:https://wiki.ubuntu.com/Nexus7/Installation
Click to expand...
Click to collapse
Really not necessary, the nexus 7 2012 forum here on xda and a google search will yield that. Completely different SoC and other peripherals don't let the tutorials carry over.
dwegiel said:
The first is for the original nexus 7, seeing how it is Tegra3.
Click to expand...
Click to collapse
There is a small addition there that flo's version boots but display doesn't work. I've also found attempts to run graphics via libhybris (build.merproject.org/project/packages?project=home%3Acxl000%3Anemo%3Adevel%3Ahw%3Agoogle%3Amsm%3Anexus7) but I never managed to try Mer.
Hi guys.
I managed to get the basic linux kernel v3.16-rc6 to work on the Nexus 7 2013 (WiFi).
Turns out the debug cable I originally used (delta.fratler.de/154-nexus-7-uart-unlocked/) works perfectly fine.
I use the qcom_defconfig as base and will work my way up from there, creating a n7-device tree.
In order to get linux to talk to you via the serial port, you'll need a couple of fixups though.
Namely:
codeaurora.org/cgit/quic/kernel/skales/plain/atag-fix/fixup.S – this is due to the fact that the N7 bootloader hands over the wrong memory-mapping in its ATAGS (shifted by 2 MB)
Compile it with
gcc -c fixup.S -o fixup.o; objcopy -O binary fixup.o fixup.bin
Then merge the fixup, kernel and the dtb:
cat fixup.bin zImage dtb > bootImage
Next up, to prevent the console from freezing, you need to grab this file from the qcom repo over at linaro:
git.linaro.org/landing-teams/working/qualcomm/kernel.git/commit/a751c4d71e792784f4d9f399bfda04007a6f403d
Note that the UART-port has been renamed from ttyHSL to ttyMSM.
Here's the kernel-config I used (based on qcom_defconfig): paste.debian.net/113411/
Once the dts resembles something remotely useable, I'll post it as well
dTatham said:
I managed to get the basic linux kernel v3.16-rc6 to work on the Nexus 7 2013 (WiFi).
Click to expand...
Click to collapse
This is great! Did you manage to have ssh there at least? I don't have UART cabel, but I'd really love to help you with this
vrutkovs said:
This is great! Did you manage to have ssh there at least? I don't have UART cabel, but I'd really love to help you with this
Click to expand...
Click to collapse
Unfortunately not yet.
I'm currently having some issues getting USB to work. The patch to implement the QCOM PMIC8921 extender's GPIO ports has only been submitted 2 weeks ago and I have yet to figure out how to implement it in the devicetree - If anyone can give me some pointers to that...
I'll set up a github repo for the linaro kernel with the Nexus 7 dts this week. Once I have some rudimentary support (USB, eMMC, WLAN), I'll start upstreaming.
Still no real progress but things on the linux-arm-kernel mailing list have been moving pretty quickly so I hope we'll have a decent patch set within the next two weeks or so.
In the meantime, I wrote up a basic guide to get things started if you're interested in porting a vanilla kernel to the N7:
delta.fratler.de/168-nexus-7-kernel/
Trying Complete Linux Installer from Play Store made me personally conclude any conventional desktop Linux UI at the moment is unfit for using on gadget display. But I wonder what takes so long to simply wireless mirror screen dual view and extended desktop to dlna, Chromecast, etc 3rd party display. Phone/tablet can then function as desktop/laptop too with ultra mobile workstation also.
Verstuurd vanaf mijn Nexus 7 (2013), iPad Mini Retina of Moto G Lte
i found this but havent been able to follow the instructions fully throught
https://github.com/crondog/arch-flo
Would be awesome if anybody made a mrom out of this etc so the development could continue faster/easyer
dwegiel said:
We already have the ability to boot multiple ROMs and plenty of kernels available. Ubuntu Touch is not being built because it is based off of CM10 (4.2) which flo/deb never ran and as a result are unsupported. However, what is stopping devs from using the kernels available to boot full ARM versions of ubuntu, debian, arch or gentoo? I've looked at the nexus 7 2012 and there has been plenty of such development, even sooner after its release. Is this nexus doomed to solely run android due to the qualcomm processor it possesses?
Also, please note, I'm not looking to run linux INSIDE android (chroot method). That is possible on just about every android device known to mankind and nothing special. I want to run linux as a ROM. This has been previously accomplished on popular tablets like the nexus 7 2012, note 10.1 and the transformer prime, just to name a few.
Click to expand...
Click to collapse
Ubuntu Touch Is Available.
See MultiROM Manager.
Recently I installed Windows 10 RT on my Surface RT.
I think it's better than the Windows 8 RT and most people can agree on that.
Even after having W10 OA, there are not many apps available for this device.
I was wondering if anyone successfully built a version of android that ran on ARM Windows devices. I would like to build one compatible for the Surface RT but there are no kernel sources or device trees available. Also, there is no way to flash it with a conventional flash tool. Therefore, it cannot be built this way. But has anyone tried compiling android x86 but for ARM?
If yes, in which way did you build it?
Or if you built it in another way, in which way did you build it?
I am very interested in building a version for our Surface RT so we can finally get somewhere and get support for almost all of the apps in the android world
alexenferman said:
Recently I installed Windows 10 RT on my Surface RT.
I think it's better than the Windows 8 RT and most people can agree on that.
Even after having W10 OA, there are not many apps available for this device.
I was wondering if anyone successfully built a version of android that ran on ARM Windows devices. I would like to build one compatible for the Surface RT but there are no kernel sources or device trees available. Also, there is no way to flash it with a conventional flash tool. Therefore, it cannot be built this way. But has anyone tried compiling android x86 but for ARM?
If yes, in which way did you build it?
Or if you built it in another way, in which way did you build it?
I am very interested in building a version for our Surface RT so we can finally get somewhere and get support for almost all of the apps in the android world
Click to expand...
Click to collapse
Sounds like a good idea, another option would be to look into the Linux4Tegra side of things, I'm not sure if it supports the Tegra 4 in the Surface2 but if it does we might have some interesting things to draw out of it...
AlGaib said:
Sounds like a good idea, another option would be to look into the Linux4Tegra side of things, I'm not sure if it supports the Tegra 4 in the Surface2 but if it does we might have some interesting things to draw out of it...
Click to expand...
Click to collapse
Actually, there are suprisingly still people working on linux: https://forum.xda-developers.com/wi...-secure-boot-linux-surface-rt-t3653848/page12
First we have to get linux and then we can adapt the kernel and drivers to run android. There are very similar tablets running android like the ASUS Transformer Pad TF502T. If we use this kernel tree and build a device tree, we should get it working. I would try Lineage OS and TWRP. I think we can get maximum android Nougat for this tablet, after that, because of big kernel changes on android oreo+, we have to modify it even more. Forget about android X86. It's not a great idea.
I have compiled android custom roms before, but with all of the sources ready. In this case, we have to build a lot.
CrackTheSurface said:
Android is only a colorful touchy surface which is based on Linux, so at very first we must get Linux running.
The SoC(System on Chip) Tegra3 has Linux kernel mainline support so driver support shouldn't be that much of a problem (I am an optimist :fingers-crossed. Display output should also be possible as far as i know it uses Display Serial Interface (DSI) and is directly connected to the SoC.
The attachable keyboard is connected via i2c HID, which has also Linux kernel suppport. HDMI should also be supported out of box by the kernel. Touchscreen, WiFi, Audio, Bluetooth are the main problem points.
But now must start getting the kernel to run with an command line interface (CLI).
And installing the nvidia graphics drivers and multimedia codecs
Click to expand...
Click to collapse
If anyone wants to help with linux, please do it.