Related
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
DROPPED SUPPORT FOR VIVOW.
As we do not feel comfortable anymore in these forums, we will definately drop support for the Incredible 2.
We were wanting to give you more then a fully working one V port (such as a full sense 4 port), but since we have the feeling the community doesnt want us here, we will leave Inc2 forums.
Sirencely,
djpbx, Floatshow, htc-phones.
DROPPED SUPPORT FOR VIVOW.
As we do not feel comfortable anymore in these forums, we will definately drop support for the Incredible 2.
We were wanting to give you more then a fully working one V port (such as a full sense 4 port), but since we have the feeling the community doesnt want us here, we will leave Inc2 forums.
Sirencely,
djpbx, Floatshow, htc-phones.
Woot first
Sent from my Incredible 2 using xda premium
Thanks, downloading now. Will the tools from the One X leedroid tweaks work?
72ls1 said:
Thanks, downloading now. Will the tools from the One X leedroid tweaks work?
Click to expand...
Click to collapse
Leedroid tweaks need to be ported, but they belong to full sense 4 so actually no use on One V rom
Downloading now. I expect the main bug to be the camera but will report any I find
Added some screenshots
i flashed it to see whats what...heres some observations:
no english us as option (english gb is there though)
no data, nor recognizing vzw as carrier
wifi is borked
no soft key lights
menu button doesnt function (keys werent remapped like in newer 1.56 ports)
nitsuj17 said:
i flashed it to see whats what...heres some observations:
no english us as option (english gb is there though)
no data, nor recognizing vzw as carrier
wifi is borked
no soft key lights
menu button doesnt function (keys werent remapped like in newer 1.56 ports)
Click to expand...
Click to collapse
Thanks for your report. i'm going to take a look at them
I think English US not appearing is normal, since it has been built from the EU RUU
Just two questions:
- Going to check about the data. is Verizon using CDMA or GSM network technology?
- What do you mean with borked?
djpbx said:
Thanks for your report. i'm going to take a look at them
I think English US not appearing is normal, since it has been built from the EU RUU
Just two questions:
- Going to check about the data. is Verizon using CDMA or GSM network technology?
- What do you mean with borked?
Click to expand...
Click to collapse
verizon uses cdma (although this is a world phone too), you ll need to update the build.prop's data path accordingly in addition to the correct reference-ril.so lib
wifi wont properly connect...since i was also using the virtuous prima kernel in my latest sense 4 port i ran into the same issues....my semi conclusion is that they included the wrong bcm module w/ the rom zip
english us can be added easily by modding the default.xml
nitsuj17 said:
verizon uses cdma (although this is a world phone too), you ll need to update the build.prop's data path accordingly in addition to the correct reference-ril.so lib
wifi wont properly connect...since i was also uses the virtuous prima kernel in my latest sense 4 port i ran into the same issues....my semi conclusion is that they included the wrong bcm module w/ the rom zip
english us can be added easily by modding the default.xml
Click to expand...
Click to collapse
Thanks. What kernel would you recommend to give the Inc2? CM9 kernels also work on the Desire S so it might work too on the Inc2.
djpbx said:
Thanks. What kernel would you recommend to give the Inc2? CM9 kernels also work on the Desire S so it might work too on the Inc2.
Click to expand...
Click to collapse
the cm9 or tiamat kernel is ok, but its not nearly as stable as the virtuous one unfortunately (i used cm9 in first 4 versions of mine) which lead to some sod issues, overheating, and freezes
virtuous kernel source isn't the easiest to to build from the way its set up on github, and i asked corcor to rebuild the kernel for me to get the proper modules, but it wouldnt boot...ill ask cjward or one of the guys for help with it next week if i remember to
Hotfix 1 attatched to this post.
Install this right after a fresh flash.
It has been tested and it works. It will be included in the next version.
djpbx said:
Hotfix 1 attatched to this post.
Install this right after a fresh flash.
Please report if it makes the cellular and data work.
if it works it will be included in the next version of SenseMOD FlashONE
Click to expand...
Click to collapse
I just tested this out for you and its working
gaby04 said:
I just tested this out for you and its working
Click to expand...
Click to collapse
I'm out of thanks for today so i'll just thank you the hated way
thanks mate! the fix will be in the new version.
Hey man digging the rom very nice work I'd stay but I need WiFi
Update time!
Bugs fixed:
- removed USB debugging notification from every device: (build.prop persist.adb.notify=0)
- Incredible 2: fixed no recognizing Verizon (WORKING)
- Fixed Inspire 4G Mic and sound
- Fixed installation of 3D rosie.
- Added Bluetooth Audio mod for SAGA
- Added Bluetooth Audio mod for ACE
- Added manual device selection in AROMA.
- Fixed home button problem for Desire S
- Fixed menu button problem for ALL devices.
- Desire Z bootfix
DOWNLOAD: http://sb-boardteam.nl/sensemod-flashone/SenseMOD_FlashONE_v1.2.zip
djpbx said:
Update time!
Bugs fixed:
- removed USB debugging notification from every device: (build.prop persist.adb.notify=0)
- Incredible 2: fixed no recognizing Verizon (WORKING)
- Fixed Inspire 4G Mic and sound
- Fixed installation of 3D rosie.
- Added Bluetooth Audio mod for SAGA
- Added Bluetooth Audio mod for ACE
- Added manual device selection in AROMA.
- Fixed home button problem for Desire S
- Fixed menu button problem for ALL devices.
- Desire Z bootfix
DOWNLOAD: http://sb-boardteam.nl/sensemod-flashone/SenseMOD_FlashONE_v1.2.zip
Click to expand...
Click to collapse
Damn. Just got done downloading the first one.. lol.
Sent from my Incredible 2 using xda premium
djpbx said:
Bugs:
WiFi tethering
Camera
Games like Temple Run
Click to expand...
Click to collapse
Are those the ONLY known bugs? (I know this sounds newbie but want to make doubly sure!)
I am trying this out today! Wanted to try some sense 3.5/4.0 like OpenSense4 but it has bucket loads of bugs. So I am very surprised that this is as good as AOKP, bug list wise... Thank you djpbx and Floatshow!!!
P.S: More people thanked post #2 than #1. Come on, people! Give the OP some love.. He worked on it too... (I expect equal # of thanks on both)
litetaker said:
Are those the ONLY known bugs? (I know this sounds newbie but want to make doubly sure!)
I am trying this out today! Wanted to try some sense 3.5/4.0 like OpenSense4 but it has bucket loads of bugs. So I am very surprised that this is as good as AOKP, bug list wise... Thank you djpbx and Floatshow!!!
P.S: More people thanked post #2 than #1. Come on, people! Give the OP some love.. He worked on it too... (I expect equal # of thanks on both)
Click to expand...
Click to collapse
At best this is as functional.as opensense
But it has all the same bugs (though pre 0.5 os has working Wi-Fi)
Just sharing my observations
** 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 :/
What is this:
This is Stuxnet a custom kernel for Android, this kernel focuses on simplicity and stabiilty. All features on this kernel are based on long hours of testing and all are thoroughly tested to give end users the best experience for their device.
Stuxnet is mostly stock with optimizations and features that are often used by users that are not affecting performance on their device. Future development of this kernel will focus on Performance and Stability.
So enough with the intro and start testing this on your device.
Features:
Based on Xiaomi kernel source
Fully Optimized Kernel
Sound Control
FSYNC Control
Voltage Control
MSM Hotplug
Thermal Enhancements
USB Fast Charge
Check Github and/or Gitlab for full changelog
How To's:
Install in recovery
No need to wipe (unless you want to wipe your a$$)
Reboot
Kiss yo' mama
***** Slap an iPhone user.. Smile!
Enjoy
Credits:
Google
CyanogenMod
Linux
SimpleAOSP
and all custom kernel devs
Download:
CM
MIUI
Kernel has two builds Stable and Nightlies
WARNING!
This kernel is only compatible on CM based ROMs.
~End
Donations:
@morpheus620 - $15
@gary138.138 - $15
@Riichard63 - $20
Thanks man!
Will test it soon! Sorry for the Noob question but can you tell me if it can be used for building cm11. I am a noob in android development.
I'm using this at the moment on XenonHD. So far everything is working. And that smoothness....its off the charts! xD Btw Dev @Gnome, can you add Lionheart and Sio on the next release?
And LCD KCAL please.
Gnome said:
One More!
Click to expand...
Click to collapse
Thanks
Sent from my MI 3W using XDA Free mobile app
I just flashed this kernel on the XeonHD 4.25 build.
Hoping that they are good partners.
This is just a preview, I'll be adding some stuff from my previous kernels soon... just checkout my git for changelogs and also check the download page for new releases.
Gnome said:
This is just a preview, I'll be adding some stuff from my previous kernels soon... just checkout my git for changelogs and also check the download page for new releases.
Click to expand...
Click to collapse
Ooohh yeaahh! E. A. G. E. R. L. Y waiting. XD
Working on Bitti09's CM12.1 confirmed
No new governors yet! Waiting!
On Revolution Remix rom, i got camera fixed, and after using the GPS fix app, it fix the gps fery fast.. so, so far everything working!
Thanks a lot, @Gnome!
Jhayzt said:
And LCD KCAL please.
Click to expand...
Click to collapse
+1
I used KCAL controls on StellAR and the difference was AMAZING! (alas StellAR doesn't gel with XenonHD for me)
SharksT said:
On Revolution Remix rom, i got camera fixed, and after using the GPS fix app, it fix the gps fery fast.. so, so far everything working!
Click to expand...
Click to collapse
*Resurrection
UPDATE: @Gnome I flashed the kernel, everything seems to be working fine (WiFi, Sound mods etc).
But call bug v1 seems to be present (touchscreen active during call)...can't comment about call bug v2 (screen-off death) yet, but I hope it's not here, cuz I plan to use this kernel as my driver...
The Dork Knight Rises said:
UPDATE: @Gnome I flashed the kernel, everything seems to be working fine (WiFi, Sound mods etc).
But call bug v1 seems to be present (touchscreen active during call)...can't comment about call bug v2 (screen-off death) yet, but I hope it's not here, cuz I plan to use this kernel as my driver...
Click to expand...
Click to collapse
Sorry, can you make difference in V1 call bug and V2.
I missed something obviously
P.s. OP thanks for 1st OPEN ANDROID development thread wort mention
Gonna try after Worker's day
sudy_freak said:
Sorry, can you make difference in V1 call bug and V2.
I missed something obviously
P.s. OP thanks for 1st OPEN ANDROID development thread wort mention
Gonna try after Worker's day
Click to expand...
Click to collapse
Yeah, call bug v1 is something most ppl who recently joined the Mi3 forums won't have faced.
It is one of the major bugs (aside from deep sleep reboot) that was there in the original Lollipop ROMs for cancro. It was fixed a long time ago (by audahadi and Bitti I believe, as Ivan's ROMs had the bug for a long time afterwards too).
The bug was that the touchscreen would remain active when you're in a call and the proximity sensor turns the screen off. It would cause the notification/quicksettings panel to be pulled down or brightness to be changed due to contact with ear or cheeks. Other more complex things could also happen like when I once turned on Airplane mode while talking and got disconnected :laugh:
And call bug v2 is a new bug that seems to affect ROMs (except I believe Ivan's AOSP and SOKP which switched to Ivans kernel I think) since 5.1...
While calling (or sometimes VERY RARELY while doing something else) the phone kind of hangs, the screen goes dark and it goes into a screen of death mode. Nothing can be done, your only option is to press and hold Power button for a very long time (approx 12-15 secs; much longer than a normal hard reset ~8secs) to hard reboot your phone.
Hope you got it. :good:
PS. Yes, try this kernel. You won't be disappointed.
Added some under the hood stuff on 3rd build, also check if fast charge works, since it works fine on my end.
Gnome said:
Added some under the hood stuff on 3rd build, also check if fast charge works, since it works fine on my end.
Click to expand...
Click to collapse
Thanks Dev @Gnome! I'm trying it at the moment.
Wow, using alpha 3 working great even on temasek 10.6 by moonlight, just waiting another hotplug, IO Scheduler, CPU & GPU Governors, btw can you make a little downclock and overclock cpu freq tables? Thx for great kernel....
Gnome said:
Added some under the hood stuff on 3rd build, also check if fast charge works, since it works fine on my end.
Click to expand...
Click to collapse
Fast charge!
Very useful!
I'll try this asap.:laugh:
@Gnome , Buddy thanks for your work gonna try it soon
just a query
there are two build dated 30-4-15
Alpha 3 and Alpha Z
whats the difference which one to flash
ZenR2 said:
@Gnome , Buddy thanks for your work gonna try it soon
just a query
there are two build dated 30-4-15
Alpha 3 and Alpha Z
whats the difference which one to flash
Click to expand...
Click to collapse
dont mind the Lettered version, just flash the numbers.
Gnome said:
dont mind the Lettered version, just flash the numbers.
Click to expand...
Click to collapse
buddy flashed the alpha 3 build , but now wifi is not working on latest Xenon Hd rom
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.