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
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 :/
Okay everybody, I want to start a WIP on this as it seems that we can get somewhere. The last dev seems to have dropped the project so I picked it up. :good:
***NOTE*** This is meant for development/testing purposes ONLY. It is in NO WAY for the faint of heart and you must follow ALL instructions or it will not boot! You have been warned!
As of 5/7/2013, the following things are working:
Camera (flash works, it takes pictures)
Sound (the only reason I know this works is because the shutter noise goes off in the camera app, there is no other way to test this right now)
The test apps (browser, notepad, gallery, camera, browser, phone, calculator, calendar, clock)
Power button (phone goes to sleep and wakes, hold the power button down to shut off the phone - the shutdown takes a second because it shuts down just like a linux kernel would - plug it in the charger to test this, it will vibrate once it is off)
Not working - just about everything else. Most items are still placeholders and there is a stability issue where the apps all close themselves after a few seconds which I am trying to figure out. There is no data or cellular connectivity of any kind. This may be fixable, however, since I was able to get the camera working by pulling the prebuilts from a different CM version. I'll keep experimenting with this. If you put the device to sleep, it does not wake up to the same brightness (it is dimmed) and you can not adjust the brightness right now (working on this as well, its a permissions issue in the kernel source but I haven't been able to narrow it down yet).
It is VERY finicky about how it is installed. I won't give any support for anything but TWRP 2.5.0.0
To install:
-Download the kernel zip and the latest daily from Ubuntu (I will post links later)
-Backup your current ROM in its entirety using TWRP - check every item on the list or you may have to go to a fresh install of your version you were running previously.
-In TWRP (once again, make sure its 2.5.0.0 because these are 2.5.0.0 specific instructions), factory reset but do an advanced reset, check dalvik, data, system, and cache. ***MAKE SURE THAT YOU DON'T FORMAT YOUR MICROSD***
-Install the kernel zip and do not wipe cache or dalvik
-Install the Ubuntu preinstalled image, once again make sure you do not wipe the cache or the dalvik.
-Do not do anything else, no fixing permissions or anything, just reboot
-Wait about 2 minutes for the lock screen to come up and then you can use it
I will keep working on the kernel - the other functions will not work until Ubuntu implements them.
This is my first time working with actual development - if anyone wants to give me a tutorial to get my project up on GitHub so everyone can work on it, I would be more than happy to do so.
Here are the links:
Kernel built 5/7/2013: http://d-h.st/185
Latest Ubuntu Touch base: http://cdimage.ubuntu.com/ubuntu-to...current/raring-preinstalled-phablet-armhf.zip
Since the source has been moved to Raring Ringtail, there should not be a need to update that link. Please note that the 5/7/2013 build is the one that I tested and be sure to let me know if it gets broken in the future.
Enjoy everyone and once again, if you want to contribute, I'm more than happy to set up a GitHub, I just need some basic help getting it started.
Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium
TheLastSidekick said:
Thanks this looks very hopeful.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I am hoping that development will take off. Ubuntu is set to start releasing alpha apps on the 16th so figuring out how to get a working kernel for it was top priority for me and nobody else seemed interested in doing it.
I've literally spent hours, lots of expletives, and other unpleasant things trying to get this built. I think I should have started working with CM BEFORE taking on UT but it paid off
Thank you sir,
Dling now
Sent from my Galaxy Nexus using xda premium
Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium
ktetreault14 said:
Flashed and everything went smoothly. Very pre-alpha, but alot of.stuff is working comsiderinf whaf it is. I wluld like to test this for any developer that wants to build it
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.
EtherealRemnant said:
I'm glad that you enjoyed what currently works.
I have done some work on the kernel but I need some help figuring out the WiFi. The drivers are proprietary Broadcom drivers so I need to see if anyone has gotten it to work on their Touch builds.
The rest of it is mainly just waiting on Ubuntu to stabilize - this isn't even considered an alpha at this point. Alpha starts May 16th.
Either way, I've managed to compile a kernel using cm-10.1-M3 (4.2.2) sources in preparation for UT's inevitable source upgrade from M1 (4.2.1) to M3. I'd post it but it doesn't have any different features from the M1 kernel up above.
I'll be updating it as Ubuntu releases new features or if I can get other things working on the build.
Click to expand...
Click to collapse
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium
eggydrums said:
So, Ubuntu is using android stuff for these builds?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The kernel is a CM base. Its a massive fork of CM that's kind of a royal pain in the ass to work with since its not been synced since they forked it and they've made major modifications to the code (all traces of Dalvik are gone, for example). You also have to make modifications to the kernel build so it functions more like a linux system, there are process patches that have to be applied to the kernel, etc.
Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.
Cannot wair for Ubuntu to be fully released, I would like to use this as a daily driver
Sent from my SGH-T999 using xda premium
charlieb620 said:
Thanks for keeping this going. Not much is going on until Ubuntu pushes things out later this month. Everything will pretty much FC until we have the proper scripts.
Click to expand...
Click to collapse
So you had the same issue with your build?
Admittedly, I never tried it because I was determined to build my own and yours was March dated. I had posted in the thread trying to get some assistance from you actually - but yeah, its certainly not usable right now.
Was your kernel a forced M1 or did you somehow find a way to get the nightly source to build? I've built M1 and M2 so far. Since I had the same results with both and UT is based off of M1, I haven't messed with M3.
I wish I could figure out the WiFi and the force close of apps - did you patch the kernel successfully? I added the proc patch as best I could (raw data paste but it didn't throw warnings so it must have worked - I'm not a programmer) and it didn't fix anything, apps still just close after a few seconds.
I was surprised that I got the camera and sound though just by switching CM versions. Maybe the same thing can happen with the WiFi? I noticed that it is being built as a module but I don't know enough about the Android kernel to reconfigure it as a built-in (I don't know if the Ubuntu kernel has the code for detecting all the hardware just yet, I'm guessing it doesn't). I've done lots of Linux kernel tweaking (I have toyed with it since Red Hat 1.0 and its my daily driver in the form of Ubuntu 13.04 right now - usually I use Mint but I wanted to eliminate as many variables as possible) but I don't know much about Android.
Admittedly, I started with UT before I had ever worked with CM even so I've learned a LOT. lol
Thanks for this.
So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app
biohazard said:
So does this kernel work with the latest UT Developer Preview release? If not I would be willing to help you getting it back up to date even though I'm still a newbie! Thanks in advance for the response.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It should work fine with the latest DP. I haven't bothered to update it because the kernel source hasn't really been worked on. They're still focusing all of their work on Google devices.
There isn't a stable kernel for any S3 variant right now.
Sent from my SGH-T999 using Tapatalk 4 Beta
Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium
biohazard said:
Mmmm, I can't seem to get it to boot at all.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Make sure you followed the directions exactly, any deviation will cause it not to boot. Also there is no boot screen. What you can do is plug it in to the charger before you boot it - if it fails to boot the phone will power off and take you to the charging screen. If it doesn't, give it a few minutes to load up especially the first boot.
If it fails again, let me know and I'll see about building a new kernel some time this week. As far as I am aware there is no newer kernel source on the Ubuntu side but I can try to build an RC5 based kernel (this is an M1 kernel).
Its worked for everyone else but I can't test it right now because I'm getting ready to go out and need my phone.
Sent from my SGH-T999 using Tapatalk 4 Beta
Alright I see, thanks for all the help. Could you possibly point me to the correct base download, I have tried multiple phablet bases, and I just can't get it to boot for some reason. Thanks in advance for all the help.
Sent from my SGH-T999 using Tapatalk 4 Beta
The international GS3 has working wi-fi.....i know the hardware is completely different but do you think you might be able to look at how they got it working over there?
http://forum.xda-developers.com/showthread.php?t=2315397
Here's the commit that shows how he got wi-fi working: https://github.com/Androguide/andro...mmit/feac1d9af58c2947e0f3f6b6719553be5811ce6d try applying that to init.qcom.rc i would but my computer won't build anything i'm trying to fix it...
Also for github you really just need to post your manifests file and whatever you've modified from the source code. i'm not really a pro with github but i've worked with it quite a lot. They have an awesome tutorial on their website i'd recommend checking out.
Okay Ubuntu made upstream code changes that broke the kernel. Give me a few days and I'll have an update.
Plays2 - that patch *should* work for us as well since we use Broadcom's WiFi just like the international version does (odd that they didn't use Qualcomm's since it came with the SoC but it works in our favor in this instance). Still takes a lot of configuration to get it running though.
Hi! This is my first mod for Android; a partially working attempt at getting the Samsung camera (from the leaked 4.2.2 ROM; XUFME7) to work on AOSP ROMs. Not a skin, this is the full camera along with most of the features!
Want to see it in action? No screenshot - it looks exactly the same as on TW ROMs - but here's a video. http://www.youtube.com/watch?v=mYX4PSVDiIU Apologies for the terrible quality, but it's hard to film a phone with the Nexus 7's front camera, and I couldn't find a decent screen capture app :<
--
Port for Android 4.3
Beta version NOW AVAILABLE, click here for details + download: http://forum.xda-developers.com/showpost.php?p=46566446&postcount=135
It doesn't work as well as the 4.2.2 version - in particular, video recording is 100% broken, even in the AOSP camera - but you can still try it out if you don't mind this!
--
Port for Android 4.2.2
Working/Non-Working Features List:
What Works:
Front and back cameras
"Wand" Filters
Flash
Auto & Macro focus modes
Tap-to-focus
White Balance options
GPS tagging
Gallery shortcut (uses AOSP Gallery)
Shooting modes:
Single Shot
Best Photo
Face Detection
HDR
Beauty
Smile Shot
Low light
Possibly Working, depending on kernel:
(These features require that the mediaserver process can write to /sdcard (for burst shot/best face) and /data (for panorama). The only way to change this is using a modified kernel with an init.rc which gives it that access. In my experience, with Googy-Max kernel, Panorama works but the other two don't. Your mileage may vary.)
Burst shot
Best Face
Panorama
Not Working, may be fixed later:
Shutter sounds
Automatic mDNIe / screen brightness adjustment
Not Working, unlikely to be fixed:
Camcorder
Share Shot
Voice recognition
Weather/city photo tagging in the media database (what's this used for exactly?)
Untested:
Buddy Photo Share
External SD card
Download:
Download:
This patch is ONLY compatible with AOSP-based 4.2.2 ROMs running on the GT-I9300 and GT-I9300T; the international models of the Galaxy S3 (Exynos chip, no LTE)
CWM zip: http://d-h.st/sg8 (5.26 MB / MD5: f53d603f49de1bb0aba90546b9bbc1ce)
Notes:
This patch has only been tested on RootBox 4.1. Please let me know if you have trouble using it on any other ROM!
Disclaimer:
This is an experimental patch, and you install it at your own risk! I am not responsible for anything that occurs as a result of this. Always make backups.
Installation:
You need a recovery that allows you to install .zip files; most likely CWM or TWRP. But you probably already have one of these if you're running AOSP on this phone
1. Boot into recovery mode: turn the phone off, hold down VolumeUp+Home and then press the power button
2. Make a Nandroid backup (not obligatory, but recommended in case something goes wrong!)
3. Flash the camera mod zip
4. Wipe the Cache and Dalvik Cache - just in case
Hope you enjoy it! Now go out and take some awesome photos
Changelog:
20th July 2013: Released first version. Camera (+ most features) is functional. Camcorder appears but does not record successfully.
22nd July 2013: Released new version which should work on any AOSP ROM, instead of needing a custom built ROM.
17th October 2013: 4.3 beta release is out.
Hm, I'm guessing that the picture quality isn't different from the AOSP camera app and this tho there still is missing sources from Samsung that we'll never get.
Otherwise. Nice mod!
Eleve11 said:
Hm, I'm guessing that the picture quality isn't different from the AOSP camera app and this tho there still is missing sources from Samsung that we'll never get.
Otherwise. Nice mod!
Click to expand...
Click to collapse
Thank you
I've seen people talk about how the camera on AOSP is worse because of missing sources, but I'm not sure what sources these are. The Samsung kernel module is open source, and this mod replaces all the user space code related to the camera - as far as I know, anyway - with the TW versions. (Please correct me if I'm wrong on this )
This is purely anecdotal and rather hard to test accurately, but I never noticed much of a difference in picture quality between AOSP and TW, I just wanted the camera app because of the extra modes and options that are really useful.
I was not Using AOSP based ROMs only for the sake of camera.
But now, i can use any ROM i want..
Thannks man.. This is super cool.. will test this ASAP..
Well, the full version method didn't work for me on todays' CM nightly build. I installed it following the procedures, and then opened the camera app. The screen went black, and then froze. I restarted the phone, and it kept looping on the boot animation
Luckily I don't delete the CM updater temporary files, so I was able to boot into recovery and re-install the 'stock' CM build. Also, despite the fact that I mostly understood the instructions, they were quite confusing!
does hdr work? is it like the tw cam?
Sent from my GT-I9300 using xda app-developers app
kuci06 said:
Okay, so I just flashed the modified Rootbox rom, and the burst shot feature does not work properly. The little counter bar comes up, but doesn't shoot photos at all. Also breaks functionality after that, not even the close button works.
Click to expand...
Click to collapse
Just as I expected I'll have to figure out a fix for this somehow...
Writing to /data does seem to work, so maybe I can patch the Samsung lib to store burst shots there, and move them to the SD card from the camera apk :x
iSasha said:
Well, the full version method didn't work for me on todays' CM nightly build. I installed it following the procedures, and then opened the camera app. The screen went black, and then froze. I restarted the phone, and it kept looping on the boot animation
Luckily I don't delete the CM updater temporary files, so I was able to boot into recovery and re-install the 'stock' CM build. Also, despite the fact that I mostly understood the instructions, they were quite confusing!
Click to expand...
Click to collapse
Apologies for the confusing instructions :< I think I got carried away a bit with the technical details!
You cannot use this mod with an existing build of another ROM (like the CM nightlies) unless it has been compiled with the source code patches I provided. Samsung's camera libs are not compatible with normal AOSP builds, but my patches change the interface in AOSP to fix that.
It's a bit of a lofty goal but I hope that other ROMs will some day include these patches, because it doesn't affect normal camera operation, and it allows you to use the Samsung camera if you flash the appropriate libs...
I would like to provide builds of other ROMs in the future, but this is difficult to do because it takes me 2-3 days to download the source code of each ROM and 8 hours to compile it from scratch - this is why I only have RootBox right now. So it would be extremely helpful if other developers would integrate this.
Notor1ouS- said:
does hdr work? is it like the tw cam?
Click to expand...
Click to collapse
HDR works perfectly Exactly like in the TW 4.2 camera, you get an Options menu with Normal/Strong HDR effect and with the option to save original/HDR photo or just HDR.
Treeki said:
Apologies for the confusing instructions :< I think I got carried away a bit with the technical details!
You cannot use this mod with an existing build of another ROM (like the CM nightlies) unless it has been compiled with the source code patches I provided. Samsung's camera libs are not compatible with normal AOSP builds, but my patches change the interface in AOSP to fix that.
It's a bit of a lofty goal but I hope that other ROMs will some day include these patches, because it doesn't affect normal camera operation, and it allows you to use the Samsung camera if you flash the appropriate libs...
I would like to provide builds of other ROMs in the future, but this is difficult to do because it takes me 2-3 days to download the source code of each ROM and 8 hours to compile it from scratch - this is why I only have RootBox right now. So it would be extremely helpful if other developers would integrate this.
Click to expand...
Click to collapse
Oups... I just copied over the lib and camera files over using a root explorer app. I doubt that I'll have the patience to wait days to build it form source myself, but I'll be looking forward to see these libs integrated in future versions of CM!
"Not Working, unlikely to be fixed:
Camcorder"
is that a typo for "cam recorder" ? or cam recording is working just fine?
AvivEliyahu said:
"Not Working, unlikely to be fixed:
Camcorder"
is that a typo for "cam recorder" ? or cam recording is working just fine?
Click to expand...
Click to collapse
Camcorder is a term for video recorder.
Also op thanks this mod hope it gets implemented in the rom I'm using!
Sent from my GT-I9300 using xda app-developers app
@Treeki would you continue to publish updated Rootbox Nightlies with this camera every time Rootbox is updated?
EDIT: I also think you should move this to Android Development forum instead of apps and games because you are working on a ROM based of Rootbox sources... Not just the app itself..
Sent from my GT-I9300 using Tapatalk 2
sorry for quick quesrion...
if i merge this to rom, will it just replace the original cm camera or cm camera is still there and it make new icon for the sammy camera?
Sent from S3, power By Temasek'Rom and Kernel!
I'm quoting the answer provided on the Original Thread...
Treeki said:
.
It's a bit of a lofty goal but I hope that other ROMs will some day include these patches, because it doesn't affect normal camera operation, and it allows you to use the Samsung camera if you flash the appropriate libs...
.
Click to expand...
Click to collapse
If I'm not wrong it doesn't break CM Camera, it just helps Sammy camera to Partially work...
Sent from my GT-I9300 using Tapatalk 2
thanks~
Sent from S3, power By Temasek'Rom and Kernel!
jimbo77 said:
@Treeki would you continue to publish updated Rootbox Nightlies with this camera every time Rootbox is updated?
Click to expand...
Click to collapse
Hm.. that's something I hadn't thought about yet :x
I will try and publish a new one every few days but I don't have the resources to make daily builds, unfortunately...
Now that I have some more experience with the Android build system and I know exactly what needs to be changed, I'm going to look again at modifying the Samsung binaries to work with any AOSP ROM instead of doing this the other way round. That was my intention when I first started the project, but I changed tactics because I wasn't sure exactly how much I would need to modify.
I don't know if I'll succeed at this but I'll give it a shot ... If I could get it to work, it would be a much better solution because it should work on practically any ROM with just a flashable zip. Can't promise anything yet though :<
Treeki said:
Hm.. that's something I hadn't thought about yet :x
I will try and publish a new one every few days but I don't have the resources to make daily builds, unfortunately...
Click to expand...
Click to collapse
Well, the Rootbox Nightlies doesn't come out every day as well so I think it will be nicely timed with you, btw if you ever want a beta tester of some sort.. Shoot a PM and I'll be more than glad to help...
I'm a Rootbox user since long time so it will not affect me to try your builds...
Sent from my GT-I9300 using Tapatalk 2
Welp.
I was going to post a picture of myself facepalming... taken with the TW camera app, of course... but I figured XDA is just a bit too public for that.
It turned out that one single byte in mediaserver was all I needed to change for my original attempt from several days ago to work. I wish I had known that before I started all this stuff about compiling ROMs... I suppose it was a good learning experience, though. I really didn't expect the fix to be that simple.
So my final mod turns out to be much, much simpler:
- Use Samsung files, with one modified to add a version of Camera::connect that only takes one param
- Modify mediaserver to allocate a CameraService that is 12 bytes bigger than the AOSP version
I feel kinda dumb now. Oh well! Hindsight is 20/20. And... sometimes the simplest solutions turn out to be the right ones
I'll put together a CWM zip that should [hopefully] work on all ROMs and add it to the OP shortly! Now available. Please try it out and let me know how it goes, and what ROM you're using! Off to sleep now, at the very appropriate time of 9am...
It is working correctly on the temasek rom. Thanks a lot.
Treeki said:
Not Working, unlikely to be fixed:
Camcorder
Click to expand...
Click to collapse
first. really cool mod !!!! exactly what im waiting fot
Q
is it possible to change the shortcut to googlecam recorder , when we click on video?
and a shortcut to photosphere from sammys cam "scenes" would be cool
Gesendet von meinem GT-I9300 mit Tapatalk 2
Wow if this could be optimised with AOSP it will be perfect! Flashing it now.
Sent from my GT-I9300 using xda premium
I'm back again.
It's the Andromadus htc7x30-3.0 (andromadus_4.4 branch) source compiled by me with tweaks. At the moment I'll consider it alpha, updates will be sporadic and not necessarily better than whatever came before it.
GPL Stuff
Source
Toolchain: @Christopher83 's Cortex A8 Optimized Cross Compiler Toolchain
Branch: andromadus_4.4
Kernel Version: 3.0.x
defconfig: vision_andromadus_defconfig
And the Rest...
Instructions: Click the link below, flash in recovery (no need to wipe anything), reboot
UPDATE 22/03/14: Click "Downloads" above for latest download
Changelog
Credits: Andromadus team, and a ****ton of people who have supported open source allowing me to take stuff for this kernel, and testers (you know who you are)
XDA:DevDB Information
AlterNdromadus 3.0.x, Kernel for the HTC Desire Z
Contributors
HTCDreamOn
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-11-29
Last Updated 2014-11-29
RESERVED
RESERVED
Justin case
Justin case
Told ya I'd wait for it. Downloaded and about to install. Thanx
Hi, just a quick report from V17 I had yesterday :
Not good at all for me :
- always a little latency before acting. Really noticealble on wake up.
- Same wifi bug as in stock one (scratch after airplane mode)
- long black screen during synchros this morning
- multiple android.process.media alerts. I had to reboot twice.
- with all that I can't say if it save battery as all the reboot consumes a lot...
I went back on stock ROM which is really more responsive for me.
Will try V18 but tonight. I need my phone at work today!
Are logcats required or unusefull for you?
RE: [KERNEL][DEV][ALPHA] AlterNdromadus 3.0.x KitKat CM11 | AOSB [24/02/14]
Kéno40 said:
Hi, just a quick report from V17 I had yesterday :
Not good at all for me :
- always a little latency before acting. Really noticealble on wake up.
- Same wifi bug as in stock one (scratch after airplane mode)
- long black screen during synchros this morning
- multiple android.process.media alerts. I had to reboot twice.
- with all that I can't say if it save battery as all the reboot consumes a lot...
I went back on stock ROM which is really more responsive for me.
Will try V18 but tonight. I need my phone at work today!
Are logcats required or unusefull for you?
Click to expand...
Click to collapse
A lot of those problems will be because I mucked about with memory allocation, but that should be fixed on Alpha 18. Logcats are more useful than nothing, last kmsg is good too, both is perfect. I expect the WiFi thing will be a ROM problem, and as to the latency I'm not sure. I tried to implement a GPU on input thing, maybe it doesn't work too well. You don't have ART enabled do you? Regarding the media crashes, are these random or happen at a particular moment, e.g. playing music, games, videos?
Thanks alot
PS as these are alpha I wouldn't suggest anyone else using these during work
evrything seems to be a okay this way. the wifi from airplane mode is from the rom, noticed it before installing ur kernal. no lag here. battery seems to be holding up well. idk if its the kernal or because i have radio turned off but together they seem to be doing great. THANK YOU. only time i got lag was when i went from dyninteractive to powersave, but since evrything is going well just went back to dyn
Awww great to see you again my friend
Will test it tonight. Only for flinny's alpha3 or also AOSB 1.2.9 / 1.3.0?
Cheers
Blade
RE: [KERNEL][DEV][ALPHA] AlterNdromadus 3.0.x KitKat CM11 | AOSB [24/02/14]
BIade said:
Awww great to see you again my friend
Will test it tonight. Only for flinny's alpha3 or also AOSB 1.2.9 / 1.3.0?
Cheers
Blade
Click to expand...
Click to collapse
Yeah this is only for KitKat ROMs, so the ones you mentioned; it won't boot on Jelly Bean.
To everyone: if I were to compile a ROM, what would you think of a revival of cn.fyodor's AOSP 4.2.2 with added features? Or any other suggestions?
HTCDreamOn said:
You don't have ART enabled do you? Regarding the media crashes, are these random or happen at a particular moment, e.g. playing music, games, videos?
Click to expand...
Click to collapse
NO ART for me
Just Seeder
media crashs are random. Sometime related to nothing but it seems to happen when working and screen goes off
I had to wipe things and reboot twice to fix it
Will report if it comes back
V18 far betteer. But I still notice this latency with black screen which is longer during synchro
HTCDreamOn said:
Yeah this is only for KitKat ROMs, so the ones you mentioned; it won't boot on Jelly Bean.
To everyone: if I were to compile a ROM, what would you think of a revival of cn.fyodor's AOSP 4.2.2 with added features? Or any other suggestions?
Click to expand...
Click to collapse
personally I would like to see if we can get a newer kernel working, like a 3.4 release.
RE: [KERNEL][DEV][ALPHA] AlterNdromadus 3.0.x KitKat CM11 | AOSB [24/02/14]
bradley_e_smith said:
personally I would like to see if we can get a newer kernel working, like a 3.4 release.
Click to expand...
Click to collapse
Are you reading my mind ? I've already been thinking about porting 3.4 (with help) for a while. It would be hard though, so in the meantime any ROM suggestions?
@Kéno40 I'm not sure what this latency problem is, I'll compile a version without the GPU input handler implemented when I have time and see if that makes a difference. Other than that I really can't figure out why you're having a problem, it's fine for me at least. What do you mean by synchro?
HTCDreamOn said:
Are you reading my mind ? I've already been thinking about porting 3.4 (with help) for a while. It would be hard though, so in the meantime any ROM suggestions?
@Kéno40 I'm not sure what this latency problem is, I'll compile a version without the GPU input handler implemented when I have time and see if that makes a difference. Other than that I really can't figure out why you're having a problem, it's fine for me at least. What do you mean by synchro?
Click to expand...
Click to collapse
I would be interested. I have compiled the lastest flinny merged with the lastest cyanogen frameworks. It boots but the camera doesn't work. So I have been looking further, but still playing around. I need to increase my virtual linux box diskspace, so I am working on reconfiguring it b/c of lack of diskspace.
I would love to see AOSP KK rom for our device. Just plain and simple.....(thats just my opinion, dont know about others)
Thanks...
Sent from my HTC Vision using xda app-developers app
And how about BT call audio? Is it working correctly with your Kernel? It is the only think I am missing wiht all the KitKat ROMs and it is definetely Kernel drivers fault... to be honest... the only roms that had it working since GB were those of 4.2.2...
And for me it would make a big help for my phone usage, cause I spend lot of the time in the car...
HTCDreamOn said:
@Kéno40 I'm not sure what this latency problem is, I'll compile a version without the GPU input handler implemented when I have time and see if that makes a difference. Other than that I really can't figure out why you're having a problem, it's fine for me at least. What do you mean by synchro?
Click to expand...
Click to collapse
In fact I don't use the lockscreen so when I tackpad wkae it, I arrive to the homescreen. But- I notice with it a little latency / black screen for less than half a second, but noticeable.
I cut Synchro during night because of the wifi problem. On the morning I put it back. It goes to slleep (the phone, not me ! ). If I wake up, I have a 1-2 seconds black screen.
RE: [KERNEL][DEV][ALPHA] AlterNdromadus 3.0.x KitKat CM11 | AOSB [26/02/14]
bradley_e_smith said:
I would be interested. I have compiled the lastest flinny merged with the lastest cyanogen frameworks. It boots but the camera doesn't work. So I have been looking further, but still playing around. I need to increase my virtual linux box diskspace, so I am working on reconfiguring it b/c of lack of diskspace.
Click to expand...
Click to collapse
I'm gonna try Paranoid Android, CM10.2 (Android 4.3) base unless anyone has objections to 4.3, it was stable and working as far as I remember. I don't know if 4.2.2 can be used for PA anymore.
arunal_123 said:
I would love to see AOSP KK rom for our device. Just plain and simple.....(thats just my opinion, dont know about others)
Thanks...
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
I would love pure AOSP too but unfortunately I don't have the expertise to get it working, I'm gonna try something simpler.
Kéno40 said:
In fact I don't use the lockscreen so when I tackpad wkae it, I arrive to the homescreen. But- I notice with it a little latency / black screen for less than half a second, but noticeable.
I cut Synchro during night because of the wifi problem. On the morning I put it back. It goes to slleep (the phone, not me ! ). If I wake up, I have a 1-2 seconds black screen.
Click to expand...
Click to collapse
Which ROM are you using? I think these might be issues with Flinny's alpha 1/2.
a.s.j said:
And how about BT call audio? Is it working correctly with your Kernel? It is the only think I am missing wiht all the KitKat ROMs and it is definetely Kernel drivers fault... to be honest... the only roms that had it working since GB were those of 4.2.2...
And for me it would make a big help for my phone usage, cause I spend lot of the time in the car...
Click to expand...
Click to collapse
If it doesn't work with the default kernel then it won't work with this.
TO EVERYONE: UPDATE 26/02/14: Latest Download It has 369MB of memory available to user
HTCDreamOn said:
Which ROM are you using? I think these might be issues with Flinny's alpha 1/2.
Click to expand...
Click to collapse
Alpha 3 since weeks and with it, I don't have this latency.
I reflashed Am=lpha 3 over and problem's gone!
Kéno40 said:
Alpha 3 since weeks and with it, I don't have this latency.
I reflashed Am=lpha 3 over and problem's gone!
Click to expand...
Click to collapse
That's very weird, no-one else is having that problem. What kernel settings are you using?
To everyone: UPDATE (again): https://drive.google.com/uc?export=download&id=0B6rld7atb8yHYXBDdUxMX2NacU0
Also, would people want Paranoid Android based on 4.2.2 or 4.3?
HTCDreamOn said:
That's very weird, no-one else is having that problem. What kernel settings are you using?
Click to expand...
Click to collapse
It was on V18.
Tried V19, better. Less latency but tonight I had a black screen on the 1st incoming call I had and I missed it.
Went bak on Alpha3...
[#Intro]
Oh, and now there's these Lollipops I'm handing out. They are free as always, and they are very very delicious.
[#Why]
[#Info]
I need people testing and finding bugs if anything is going to be fixed. I might not have the Bluetooth devices you have, I might not use the camera as much as you, I might not use 4G LTE (or mobile data in general really) as much as you; you get the idea.
[#HowTo]
Latest BuildKitKat/Stable: N/A
KitKat/Beta: omni-4.4.4-20141015-toroplus-FML.zip (162.13 MB)
Lollipop/Beta: FML-AOSP-5.0-20150108-toroplus.zip (195.53 MB)
LOLLIPOP INFO:
USE THESE GAPPS: FML-GApps-5.0.x-20150101-tuna.zip (167.81 MB)
They are based on PA's GApps, huge thank you to them!
Known Issues
- Camera can be a little touchy, but it generally works.
Lollipop Changelogs can be found in the post below!
(KitKat) BETA INFO:
Beta builds are using updated GPU drivers (and an updated kernel to go with them) courtesy of @Ziyan, as well as being up to date with the latest stuff from OmniROM. NOTE: YOU CANNOT FLASH A DIFFERENT KERNEL WITH THESE BUILDS.
Currently broken with the new GPU drivers:
- Hardware Video Decoding FIXED 2014/10/06
- Hardware Video Encoding(?) FIXED 2014/10/08
- Camera (PARTIALLY) FIXED 2014/10/08
- The stock camera app (as well as Google Camera) has this weird quirk of crashing when pressing the shutter button to take a picture, however many different camera apps on the Play Store (in particular Camera ZOOM FX) work flawlessly. Video recording is generally OK, however I've been getting some reports of the audio and video being a little out of sync, so your mileage may vary...
See the Changelog post below for..... well..... changelogs.
[#GApps]
Known Issues- The screenrecord command does not work directly, however it does work via the Power menu.
- There can be a slight (noticeable, but not huge) delay when pressing the Recents or Home button.
[#Thanks]
[#Donations]
XDA:DevDB Information
FML: Fork My Life, ROM for the Samsung Galaxy Nexus
Contributors
MWisBest
Source Code: https://github.com/MWisBest/
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2015-01-08
Created 2014-10-13
Last Updated 2015-01-08
Changelog, News, Etc.
Lollipop Beta Changelogs:
- Updated the camera HAL.
This is going to be a little... fragile, at first, but in the long run it's needed. Stock camera app saves pictures now at least.
You may also notice that there's a 5.1MP resolution now (clear your camera app's data if you don't see it), despite our camera supposedly being 5.0MP all these years. Turns out the sensor's native resolution is indeed a whopping 16 pixels taller and 16 pixels wider than we've been using.
2015/01/04
- Added back some of the classic FML optimizations and more.
Built with -fstrict-aliasing flag, C++11, and the Linaro GCC 4.9 toolchain.
- Updated to AOSP "android-5.0.2_r1" tag.
As usual, the only real change was them bumping the version number.
- Improved flashing.
The speed of flashing the ROM zip is now much faster.
- Superuser is now built-in.
There's no need to flash SuperSU. You can find Superuser in the Settings app. You may have to enable the "Development Settings" menu to see it.
Some apps are a little sketchy with this Superuser though, most notably Titanium Backup. If you have issues, try flashing SuperSU.
- Video playback should be fixed.
YouTube in particular seems OK. If you have some weird format you're playing back locally I cannot make any guarantees though.
- The camera situation has improved and also regressed.
The stock camera is kinda back to the point of where it was with the KitKat Beta builds:
---- Preview works. Saving photos does not work. Video recording kinda works.
--- However:
---- The camera calibration is a little messed up. Long story, but it'll be fixed soon. So your white balance may look kinda funky, among other things.
- Audio quality is improved, with support for 192kHz FLAC as well.
This is possible thanks to a new audio resampler, which doesn't impose the same sample rate restrictions of the stock Android ones. It also has far better quality than the stock Android resamplers.
- WiiMotes can now be paired via Bluetooth.
I used to be a bit of a Wii hacking enthusiast... I think I still need to add some more stuff to make it useable as a gamepad or something, but yeah.
- Fixed location services issues.
- (toro) Fixed switching between 4G/LTE and 3G/CDMA network settings.
- Kernel changes:
Reclaimed 38MB of RAM from the carveout stuff.
Removed HDMI's framebuffer, saving an additional ~16MB of RAM. With Lollipop, MHL/HDMI out isn't working with our old HWComposer, so might as well save some RAM in the mean time.
Added overclocking support, as well as adjusted the stock frequencies a little.
Added the GPU kernel driver back into the kernel, rather than building it as a separate module.
Switched to LZO compression for the kernel. It results in a slightly larger size to the kernel, but it boots faster.
Added the "purple tint fix".
Added compiler flag to tune code for Cortex-A9 CPU.
Built with Linaro GCC 4.9 toolchain.
Older Builds:
2014/11/16
- Fixed the RIL.
(I think, still unsure of toroplus's status.)
There were a few things that went into this, and I can't really take much credit for it other than being persistent in trying to fix it.
1. rild needed a little fix-up to somewhat return it to pre-Lollipop form. Basically Google is forcing Qualcomm's junk upon the world. @dhiru1602 pointed me in the direction of some commits from rmcc to hardware/ril that fixed this part of the problem.
2. The kernel needed a commit to support some new junk related to networking in Lollipop. @Ziyan linked me to the change in question.
- Updated to AOSP "android-5.0.0_r6" tag.
Really the only change is that the build number is bumped to LRX21T.
- Switched out a couple small proprietary binaries with a reverse-engineered open-source version.
Thanks to @stargo who has really been killin' it for the Motorola OMAP devices recently, we now have a reverse-engineered pvrsrvinit binary (the executable that fires up the GPU drivers on boot-up). This is especially important because the proprietary pvrsrvinit wasn't compiled as PIE (position-independent executable). With Lollipop, they're forcing everything to be PIE, which is good because PIE is better from a security stand-point. Previously I had been adding a workaround to enable support for non-PIE, which I now don't need.
2014/11/11
- Switched back to the old OTA package format.
With Lollipop they're now, by default, flashing something similar to a system.img. I switched back to the old format. THIS IS CAUSING VERY LENGTHY FLASH TIMES NOW HOWEVER, I HOPE TO FIX THESE SOON.
- Changed the kernel to build with GCC 4.7.
With Lollipop, Google switched to GCC 4.8. GCC 4.8 has never been kind to the Galaxy Nexus kernel, I'm surprised it was booting at all in the first place.
- Added "Ambient Display".
Apparently I need to add a "pick-up" or "significant motion" sensor for it though, so it displays something when the phone is picked up.
- Fixed chromium crashing.
This fixes Browser crashing upon open, among other things. This fix has been in chromium itself for nearly 4 months now, I don't know what the heck Google is doing to AOSP to make it so FUBAR lately...
- Fixed lag in Recents menu.
Now it's smoother than KitKat's, in my opinion.
- Added back F2FS support.
F2FS is now supported again, HOWEVER, it is NOT supported on the /system partition. It really didn't do any good for /system anyway.
- Updated various icons.
The Dialer icon in particular was bothering me. Other things that aren't visible in the launcher, e.g. SettingsProvider, have been fixed as well.
- Fixed FLAC playback, among other media decoding issues.
Just needed a sync-up in the device tree with one thing that I think Google DID do a nice job of with Lollipop actually.
- Built the ROM with "WITH_DEXPREOPT := true" defined.
This basically has all the system apps compiled before flashing, to cut down on the initial boot-up time which is ridiculously long with ART.
- Changed the "Android is upgrading..." screen to prevent burn-in.
Instead of using the white Lollipop-like look, it now should show up as the old, darker theme.
KitKat Beta Changelogs:
2014/10/15
- Cleaned up the kernel.
Ziyan went over all his work not long ago and cleaned up the commit history and whatnot. He's letting me do the task of merging in the GPU driver stuff, so I'm currently just getting the kernel to a "clean slate" of sorts for other kernel devs to fork and build off of. Basically this should hopefully be the new "stock" or "Google" kernel. As a result, there's some bells and whistles missing from this build. It does however include some new audio updates that weren't in the previous kernel, which leads me to this...
- Changed audio sampling rate to 48kHz.
Previously the sampling rate has been 44.1kHz. The Galaxy Nexus supports 48kHz though! Here's what mainly sparked this change: since KitKat, the UI audio effects (e.x. touch sounds) have been switching over to 48kHz. With the Galaxy Nexus still using 44.1kHz, UI sound playback became kinda sluggish, and this was a big contributor to it. The UI sounds use the "fast track" audio path (where it tries to do as little processing as it can to the audio in order to play it with a minimum amount of latency), however a requirement of using this is that no resampling (e.g. converting 48kHz to 44.1kHz, like it has been doing currently with KitKat) can be required on the audio being played. Therefore the UI sounds were taking the "deep buffer" audio path, which has a delay to it. In switching to 48kHz, the "fast track" path is actually even faster now than it has ever been previously, and the Galaxy Nexus was already TOP OF THE LINE when it comes to audio latency believe it or not!
Another thing about this is that there is now support for playback of 96kHz audio files.
- Some updates to the camera HAL.
This hasn't fixed the situation of stock and stock-based camera apps crashing when taking a picture, but it's a start on it though.
NOTICE: Poweramp (and probably most other media players that use their own native code for audio playback rather than straight-up using the built-in Android APIs) is being pissy about the sampling rate change. If you experience issues with music playing, especially things like popping or crackling, please try Play Music or Apollo and see if your issue is still present. I know the UIs for Play Music and Apollo are pretty awful, but I can't write my own media player because I'm dealing with this camera stuff!
KitKat Stable Changelogs:
N/A
Reserved
Reserved.
Reserved
Reserved.
Finally got FML up for you toroplus guys! Sorry for the long delay.
Awesome...thank you very much MW!!!!!
Wonderful
Currently uploading this to my server and will seed until a stable version is uploaded, then I will replace it. Thank you so much for bringing life into an otherwise fading device. :crying:
Donation sent.
Downloading. Will be my second rom I try;
Beeing the beginner that I am, I have a Maguro so i couldn't install this one.
Sorry.
BennyDS said:
Beeing the beginner that I am, I have a Maguro so i couldn't install this one.
Sorry.
Click to expand...
Click to collapse
Maguro Build is Here.
I've always wondered about this rom as I saw it on the toro thread... will give it a whirl
MWisBest said:
Finally got FML up for you toroplus guys! Sorry for the long delay.
Click to expand...
Click to collapse
Running good so far! I dirty-flashed over the official Omni build I've been running. No problems to report outside of the expected camera weirdness. Play Store camera apps are all over the map in their behavior - CameraZoomFX works perfectly as you reported, Google Camera crashes like the stock camera, Focal doesn't have any display at all. Video recording works but the audio is a bit out of sync, playback is a little choppy on the phone but is smoother on my computer. VideoCam Illusion (which does its own video encoding via software) does not work at all. Video hangouts seem to work fine.
Also, I used the torch quite a bit today, and at one point it quit working and I had to reboot to get it back. It's a bit early to tell, but I'm suspicious that this ROM is affected by the same 'Camera quits working' bug as Ziyan's 'stable' OMAP kernel.
Anyway, thanks again for your amazing work!
I had the same Torch issue as stated above, fixed with a reboot. Im currently running on Ting/ a Sprint MVNO and they are known for having APN issues with 4.4.x roms. When switching to LTE in the settings, the dialer app would crash loop until I switched back to 3g/2g. Flashing an APN zip on their forum fixed the crashing, but havent been able to tell if 4g actually connects as its pretty shotty coverage in my area. But I thought Id share incase someone else is on Ting.
---------- Post added at 05:15 PM ---------- Previous post was at 05:04 PM ----------
Coming from CM 11 I guess I have been lucky as far as not having to do my own work as far as updating the Sprint Profile, and PRL as it was still within the system settings. I have been unable to figure out how to update Profile/PRL on my own as of yet. Any chance one of you may want to share this info? I'd greatly appreciate it.
New build is up.
The ROM is running smoothly with a few hiccups. I have ran into a few problems. Here's some of them that I have found so far:
1. I currently don't have root.
2. The options to "Uninstall/App info" is there but the texts aren't visible.
3. 3G to LTE switching isn't working on the 20141015 nightly build. It was on the 20141014 nightly build.
4. No Up/Down icon on the signal.
bloopblah said:
The ROM is running smoothly with a few hiccups. I have ran into a few problems. Here's some of them that I have found so far:
1. I currently don't have root.
2. The options to "Uninstall/App info" is there but the texts aren't visible.
3. 3G to LTE switching isn't working on the 20141015 nightly build. It was on the 20141014 nightly build.
4. No Up/Down icon on the signal.
Click to expand...
Click to collapse
1. Root works here on FML. THe official build of OmniROM does not include superuser, you need to flash it yourself from recovery.
2. That's been a longstanding bug with Omni on toroplus for some reason.
3. There's no 20141014 build of FML for toroplus - are you using the Omni official build?
4. That's turned off by default - Settings/Bars/Activity Indicators.
Alright, another new build to try out! I will have a couple of ROMs to try on my GNex which is a good thing!
@MWisBest...hopefully you get some donations coming in as well as Musical_Chairs since you guys are putting time and effort into providing new goodies for us.
Hopefully you get some $$$ coming in. It's going to be about a week for me to donate. One thing people don't realize is that donations don't exactly flood in for devs. I released 4 Venum Ice ET4G ROMs and 2 fully inverted black and white Note 2 ROMs including icons, all inverted apps etc. I actually got over 1000 downloads on all 6 ROMs within the first 24 hours and had excellent feedback.... I received a total of 3 donations totaling $12! Lol. What you guys are doing is harder so hopefully some people who are still here show you guys some love for not making this a thread that got closed for inactivity.... Thanks again to both of you.
Sent from my Knox-Blocked P.O.S Tab 3 running same hardware as my GNex using Xparent Gray Tapatalk 2
Wanted to give this rom a shot mainly due to the updated GPU drivers. So far a very smooth experience and pleased with it except for one major bug for my use case: Any video playback either Youtube, MX Player, etc.. after some uptime seems to fail entirely. In the case of YT it'll just sit at a black buffering screen. It'll buffer the data fine going by the progress bar as I've at times had about 1/4 of a 10-15 minute video buffer going by that indication with no playback. If I reboot the phone and give it another shot, it works.
cr08 said:
Wanted to give this rom a shot mainly due to the updated GPU drivers. So far a very smooth experience and pleased with it except for one major bug for my use case: Any video playback either Youtube, MX Player, etc.. after some uptime seems to fail entirely. In the case of YT it'll just sit at a black buffering screen. It'll buffer the data fine going by the progress bar as I've at times had about 1/4 of a 10-15 minute video buffer going by that indication with no playback. If I reboot the phone and give it another shot, it works.
Click to expand...
Click to collapse
That's the same issue as the torch issue mentioned above. It's a hard bug to track down because it takes so long to show up, and AFAIK nobody has found a reliable way to trigger it (other than just wait a day or two for it to show up). If somebody can figure out how to trigger it more quickly, I would like to try a git bisect on Ziyan's stable OMAP kernel (which is affected by the same bug) and see if I can pinpoint what is actually causing it. But without a reliable way to tell if a particular test kernel is good or not, a bisect is more or less useless.
Hi guys. How are you? I'm fantastic right now:
EDIT: Let me fix that a little...