Develop Bugs

[DEV] Fixing/Updating the HD2 kernel and missing code

Please stay ON TOPIC to kernel DEV and missing code. Don't report every bug the Android build your using is having or it will be deleted as OFF TOPIC
As you all might be knowing that hd2 is pretty much a android native device now. Its just like any another snapdragon device. The current kernel code we are using in HD2 is pretty obsolete and missing a lot of things. It more like something working at its minimal efficiency. While i was porting over all the HD2 board files getting it on par with the other snapdragon devices I found out a lot of code was missing and some was obsolete. Eg. The gsensor code from microp was pretty minimal, a lot of things were missing in microp code. I suspect that it isnt the only code, a lot of bluetooth related stuff was missing and much more. I am not really gonna work on backporting the stuff to .32 kernel so i would like the kernel devs here to backport the stuff to the .32 kernel so a lot of bugs can be fixed and stuff can be made more stable until the .37 kernel is ready. All the commits can be found here
https://github.com/charansingh/cm-kernel/tree/master
There might be some bravo or passion instances in there cuz i am comparing the code with these two devices and taking what is necessary and sometimes i have to leave my work due to some other work and forget which file i was working on so would appreciate the more bugs.
Also Mods can we get this a sticky so we can track the progress here

Yap.. i'm not a really pro developer but i suspected those bugs before.. finally a real developer suspected that.. eager to see who's going to help fixing them

charnsingh_online said:
Also Mods can we get this a sticky so we can track the progress here
Click to expand...
Click to collapse
Ok sticky for the moment to see if it helps.

@charnsingh_online
I am really happy that you put so much power in this project big respect for that.
The reason for the missing code is because most of the drivers are reversed engineerd from winmo by cotulla. Wich make it possible to make working android parts but they don't work optimal by that. Also we miss some skilled active coders. After cotulla almost everything is created by markinus he did a incredible part big credit to him but looks like he isn't that active anymore..
Current development are mostly little things a guy who sees a little part from that and a little part from that like : you, tytung, darkstone, gauner,letama, the guy from the bluetooth fix.
We probaly don't have so much real kernel programmers because they buy a native linux / android phone.

The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252

memin1857 said:
The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252
Click to expand...
Click to collapse
actually i think the gpu drivers are kinda unstable when comparing to the performance of other phones that carry the similar gpu...

@charnsingh_online
Good start.
After reading the github commits, I still don't understand what kernel devs can do so far.

Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code

hi charansingh,
i am willing to help, but i think it would be helpfull to define packets to take over.
By looking in the kernelsources it looks good to me, but i know from own expiriences with porting that i have to look deep...
best regards
trilu

charnsingh_online said:
Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code
Click to expand...
Click to collapse
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.

Ok I'll do it tomorrow n also maintain the list in the op

I may be wrong, but this thread is not supposed to become a bug fix request thread. It is aimed at developpers, so that they collaborate on a merging of HD2 specific stuff onto a cyanogen 2.6.37 kernel...
This would most likely result in the resolution of a lot of our issues, but in the mean time, [DEV] in the thread title means it is for devs only......

Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.

I looked pushed code and it's ok, at least for first few commits. But it needs some deep cleaning an optimization, also there is some bravo naming convention used in leo specific files. You should put this tree on gitorious so we can do more work on it, but anyway i will clone tree and do some cleaning and porting new stuff.

This could be of interest, and not too much off-topic.
This kernel: http://forum.xda-developers.com/showthread.php?t=966786
is being abandoned and it had some patches for performance that I think are valuable. It had linpack scores that can be achieved only with heavy overclocks on other kernels... The problem is, the source is being distributed by a .zip, no commits, nothing... the only way to get those would be to issue a diff with... something and guess where they are. Staying on topic, I've already adapted cm-kernel for another device so I think I'll be able to help when I get enough free time to spare.

D4rk50ul said:
Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.
Click to expand...
Click to collapse
Yes you are right. Unfortunately many threads like this one get's filled with off topic chatter, complaints etc. I will try to keep my eye on this thread so the dev's can communicate. If your not contributing to the DEV work on the HD2 kernel's, please don't post your wishes and thanks post as this will quickly clog up the thread. I'd hate to lose progress due to this. That's why many DEV's end up not using XDA and reverting to IRC only. Thanks
noellenchris

Hi,
Few days back there are some conversation about libsurfaceflinger.so for color banding issue http://forum.xda-developers.com/showthread.php?t=1012278 . Since Rom is changing continuesly with libs can we port the change for color issue.
HD2 GB-2.33-SENSE-2.1 LOCKSCREEN SENSE-3

tytung said:
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.
Click to expand...
Click to collapse
tytung, has any1 of you done so? please let us know..

g30rg10u said:
tytung, has any1 of you done so? please let us know..
Click to expand...
Click to collapse
No, I didn't work on 2.6.37 kernel so far.
I didn't see that charnsingh_online added a TODO list in the OP.

Fried my laptop charger. New one on way. Hd2 arrived

[ROM][06-02-13][Flinny] Andromadus - CM10[133]

Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Current Changelog below
Checkout http://andromadus.flinny.org for links/files/previous changelogs
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.

Latest version changelog.
CM10 build 133
There was an issue with the backup tool in the last build that will break gapps and your account's etc when flashing this build, the solution is to re-flash gapps at the same time as the rom and you should be fine. This build should fix it so that the next build will work as it should
Changes.
Synced with CM - Again not many changes upstream.
Basically everything relevant to our phones up to the 4th of February in the following has been merged
http://review.cyanogenmod.org/#/q/status:merged+branch:jellybean,n,z
Kernel updated to Andromadus Current - 3.0.62

For any issues you can use the following bug tracker.
http://bugs.andromadus.com/projects/vision-nightly
In the issue please include what version of the test build u are on and if another build gets released please flash and please update the issue saying the bug is still happening on 45 or whatever number.

Howdy.
Sent from my Galaxy Nexus using Tapatalk 2

Just d'loaded. Ill note down the major issues if there are any different from stable B2.
Sent from my HTC Vision using xda premium

cjward23 said:
Howdy.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
YOU!!!!!!!!!!! WHY?!!!!
darkspadez said:
For any issues you can use the following bug tracker.
http://bugs.andromadus.com/projects/vision-nightly
In the issue please include what version of the test build u are on and if another build gets released please flash and please update the issue saying the bug is still happening on 45 or whatever number.
Click to expand...
Click to collapse
Will this cover erectile dysfunction? That kid over there said he never said it had happened before he flashed flinny44..

Because.
Thanks to the andromadus devs for the opportunity!
Sent from my DZ.

So I am assuming there will be no changelog?

I found that this rom is not deodexed ?

shellin said:
So I am assuming there will be no changelog?
Click to expand...
Click to collapse
Correct and also note this comes without warranty. Flinny could post a rom that doesn't even boot. Its basically nightly build of our repos so you can use them without having to build.

So, when's the next one due? Where's the changelog? What's adb? Why would you want a lolcat? ... *snicker*
Just kidding around for a second. I'll flash, follow the updates and post if I find anything suspicious.
darkspadez said:
Correct and also note this comes without warranty. Flinny could post a rom that doesn't even boot. Its basically nightly build of our repos so you can use them without having to build.
Click to expand...
Click to collapse
Great, thanks!
Sent from my T-Mobile G2 using Tapatalk 2

Sup Flinny! /2nd page already
Sent from my HTC Vision using XDA

Unofficial changelog for Flinny44 (from beta2):
Fixed issue where power saving does not work on certain APs under certain conditions causing wifi to drop during sleep without notice. (credit to nyt)
Fixed Keyboard brightness backlight for hidden keyboard
Fixed Camera focus button
Added Statusbar IME Switcher toggle
Fixed speakerphone/on hold/mute issues
Optimized compiler CFLAGS
Russian keyboard fix
Fixed bootanimation resolution
Added camera button play/pause for music when screen is off
Merged in changes for webkit and updated to newest CM repos.
Merged in a whole bunch of camera HAL / qcom changes
Added expanded volume overlay
Those are just things I've been keeping track of, Flinny can expand on the things he's merged in himself

blk_jack said:
Unofficial changelog for Flinny44 (from beta2):
Fixed issue where power saving does not work on certain APs under certain conditions causing wifi to drop during sleep without notice. (credit to nyt)
Fixed Keyboard brightness backlight for hidden keyboard
Fixed Camera focus button
Added Statusbar IME Switcher toggle
Fixed speakerphone/on hold/mute issues
Optimized compiler CFLAGS
Russian keyboard fix
Fixed bootanimation resolution
Added camera button play/pause for music when screen is off
Merged in changes for webkit and updated to newest CM repos.
Merged in a whole bunch of camera HAL / qcom changes
Those are just things I've been keeping track of, Flinny can expand on the things he's merged in himself
Click to expand...
Click to collapse
Thanks for that
Some of those look intresting but sadly I can't be messing around with nightlies..

Posting to feel special
-Nipqer

I havent flashed a rom in a while. Its about that time me thinks, I will let you know if I come across any problems.

Nipqer said:
Posting to feel special
-Nipqer
Click to expand...
Click to collapse
You don't need to post to feel special. Those matter already know how 'special' you are Nipqer
Sent from my Galaxy Nexus using Tapatalk 2

nice

For those that haven't heard already, HTC has released the ICS kernels sources including for the Desire HD!
http://www.htcdev.com/devcenter/downloads

HD are 2.6.35 sources...
tarroyo said:
For those that haven't heard already, HTC has released the ICS kernels sources including for the Desire HD!
http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse

Now that we have source...

so now that we have source, we should be able to improve the aosp and aokp roms right? the only reason i dont use them is because of one bug in particular. i hate the low input voice volume when in speaker phone. could source help our devs eliminate that issue?

eisawi99 said:
so now that we have source, we should be able to improve the aosp and aokp roms right? the only reason i dont use them is because of one bug in particular. i hate the low input voice volume when in speaker phone. could source help our devs eliminate that issue?
Click to expand...
Click to collapse
Dastins working on that but the audio drivers used in cm are opensource drivers so jb source won't help with that one. but its being worked on.

[ROM][4.2.2][CyanogenMod 10.1 Unofficial][TF300T(G) with BL 4.2][2013-05-09]

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

CM13 Z3+ Ivy E6553 Alpha -- Secondary Testing

This is a no-frills thread.
I am looking for additional competent testers to provide proper feedback.
Testers are assumed to be experienced. Thank you.
Okay here it is.
Flash in order of appearance. Required.
cm_ivy-test_rebuild.zip
cm13_ivy_updater_system-etc.zip <--Fixes audio.
cm13_ivy_updater_bootimage_ round1.zip <-- Fixes external storage
Thanks @MotexT for initial testing and feedback.
So, working:
All CM apps; RIL; WiFi, Bluetooth; Theme Engine, Audio, Bluetooth/WiFI Hotspot work confirmed
Buggy:
Bluetooth (crashes of Bluetooth Share);
Camera (color bugs, frontal camera take photos with glitches);
Initial load/Load after reboot (glitches, performance loss - solving easy with locking/unlocking device);
AutoBrightness (small delay when switching brightness levels on the fly)
Screen Recorder
Not working:
NFC;
External SD Card;
OTG
Click to expand...
Click to collapse
Again this is alpha. This is for sinlge sim, you are welcome to test on dsds, i would be very interested in the results.
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m

Notes and Updates
NOTE
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52
Would have posted earlier but needed a smoke break *>cough<*
NOTE: this initial offering is in 3 parts due to limited bandwidth issues.
When i have resolved external storage i will upload a new build.
NFC may take a little longer.

Breathing Room
Reserved 2
@MotexT will be posting screens, as time permits, in post number 4.
Trolls will be burned.

Screenshots
Here we have some screenshots. If you need more - PM me, will add them ASAP. Also include the type of screenshot.

I'm using a single SIM version.
Please continue the work. I'll start testing by the weekend.

lukeaddison said:
I'm using a single SIM version.
Please continue the work. I'll start testing by the weekend.
Click to expand...
Click to collapse
Thanks,
If i can get you to specifically test and log screen recorder that would be great. [including during playback]
Currently it appears to function but when it comes to playback of the recorded file, playback breaks.
Thanks.
m

Hy well this thread need a clean start
And I will test it this weekend
(single sim) hopefully it works like a charm and till then i hope you fix some little bugs you mention
BTW cause I have a SmartWatch (moto360)
Does the Bluetooth restart or dont work like it should be?
Sent from my E6553 using XDA-Developers mobile app

So, a small report about this ROM. For now I'm using it two days in a row, and it's pretty stable - you can use main functions without any troubles: WiFi, RIL, Themes Engine etc. Bluetooth works great, crashes sometimes and automatically restarts - not a big deal. It's a really smooth for alpha build and could be used even as daily driver if you close your eyes on some small bugs with not so important stuff. Anyways, testers are welcome

KOALAaufPILLEN said:
Hy well this thread need a clean start
And I will test it this weekend
(single sim) hopefully it works like a charm and till then i hope you fix some little bugs you mention
BTW cause I have a SmartWatch (moto360)
Does the Bluetooth restart or dont work like it should be?
Click to expand...
Click to collapse
K, actually i don't know. But it's cool that you have a smart watch, would you mind be a tester/logger for that function in particular?
That would be great.
Thanks
m

Single sim
How to solve this？:crying:
Full selinux support is present.
MTP Enabled
installing '/sdcard/cm_ivy-test_rebuild.zip'...
checking for MD5 file...
Skipping MD5 check: no md5 file found
target:sony/cm_ivy/ivy:6.0.1/Nega_spork/76b3bfd6c4:user debug/test-keys
could not detect filesystem for /dev/block/bootdevice/by-name/system,assuming ext4
mount:failed to mount /dev/block/bootdevice/by-name/system at /system failed;no such volume
E:Error executing updater binary in zip '/sdcard/cm_ivy-test_rebuild.zip'
Error flashing zip '/sdcard/cm_ivy-test_rebuild.zip'
updarting partition details...
......done

Hi , you are most likely using the wrong recovery for your device
See here and get a correct recovery
http://forum.xda-developers.com/xperia-z4/development/twrp-xperia-z3-fota-recovery-t3346298

moonbutt74 said:
Hi , you are most likely using the wrong recovery for your device
See here and get a correct recovery
http://forum.xda-developers.com/xperia-z4/development/twrp-xperia-z3-fota-recovery-t3346298
Click to expand...
Click to collapse
it really works!Thank you

Ok cleaned this up a bit.
I don't really have much issue with discussion on GIT etiquette, and tips to keep your "house clean" as it were. I think that's a good thing with devs working together on things like that.
Here's the bottom line. If you are merging commits into a kernel you have to keep the original authorship, period. To do otherwise is kang. We all know this.
Now if some dude has some private repo where during personal testing authorship is removed, but anything merged into the public kernel or the release repo/binary maintains proper authorship, then that is a bit gray, but the user is not clearly attempting to claim authorship at all.
If anyone sees a blatant kang, or attempt to hide/claim authorship, please report to the mods for handling. If this particular point needs more discussion, please open up a thread about it and have a non flame war discussion about it.
@moonbutt74 - I do ask that you make it very blatantly sure what your public release repo is, and that your authorship is maintained, and I actually recommend you do not link your personal playground repo to avoid situations.
Thanks guys.

After looking thru all and speaking with the OP, I am closing this thread.