Nexus 7 USB Audio Support
I originally started looking into this as part of my Nexus 7 car project. Rebooting just to get USB audio working conflicted with my goal of being able to "dock and forget". It took a bit of experimenting and debugging but it's finally working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This program should enable USB audio support on your Nexus 7 - that means you are able to plug and unplug a USB sound card without having to reboot in order for it to work. Other devices should also work but I have not been able to fully test.
It works by downloading your devices services.jar which is then extracted and de-odexed if required. The necessary classes are then patched and a new services.jar is packaged up, re-odexed, re-signed and finally re-uploaded to your device. The previous method replaced the entire services.jar which turned out to be a really bad idea!
As always please let me know of any issues you stumble upon. The patching software was written quickly so there will most likely be bugs!
Instructions
Obtain a full backup of your device. This patch is experimental.
Ensure your device is ADB enabled, rooted and has busybox installed.
Make sure your PC has Java and .NET 4 installed.
Download usb-audio-patcher below and extract to a folder.
Run usb-audio-patcher.exe, the software will guide you through the rest of the process.
Flash a kernel with USB audio support. Nexus 7 Wifi kernels can be found below although any kernel with USB audio support will work.
Downloads
Software
[Windows] usb-audio-patcher-1.1.zip.
Kernels
[N7 CM10 / Stock 4.1.2] cm-10-n7-wifi-usb-audio-kernel.zip
[N7 CM10.1 / Stock 4.2.1] cm-10.1-n7-wifi-usb-audio-kernel.zip
[Timurs N7 Kernel] http://rootzwiki.com...ment-usb-audio/
Misc
[Volume Control] n7-volume-control-patch.zip - Allow media volume control when USB audio device is connected.
reserved
thenfree subject
Hi,
I was exactly looking for such program !!
I've an HTC One XL stock ROM rooted. USB Audio is supported by kernel as I can use alsa_aplay on my external USB sound card.
But I was looking for a player. Your patchs are even more interesting !
Do you think this can be working on my phone ?
As I'am newbie to Android, I don't know if I can just copy services.jar in place of my current HTC file (making backup of course) ?
Here is what I can see in /system/framework
-rw-r--r-- root root 313 2012-11-08 18:21 services.jar
-rw-r--r-- root root 2983720 2012-11-08 18:21 services.odex
Thx for help,
Vincent.
bobmorane83 said:
Hi,
I was exactly looking for such program !!
I've an HTC One XL stock ROM rooted. USB Audio is supported by kernel as I can use alsa_aplay on my external USB sound card.
But I was looking for a player. Your patchs are even more interesting !
Do you think this can be working on my phone ?
As I'am newbie to Android, I don't know if I can just copy services.jar in place of my current HTC file (making backup of course) ?
Here is what I can see in /system/framework
-rw-r--r-- root root 313 2012-11-08 18:21 services.jar
-rw-r--r-- root root 2983720 2012-11-08 18:21 services.odex
Thx for help,
Vincent.
Click to expand...
Click to collapse
To be honest I really don't know HTC tend to do alot of things to their ROMs so it could break things horribly for you.
Without a working services.jar the device doesn't even boot - it will just hang at the boot animation and you may never be able to restore the backup.
If you can get a copy of your ROM and place it on your device prior to testing then you could flash the ROM back over the top via CWM/TWRP to restore the original services.jar file without losing your user data.
I would be interested to hear how you get on should you decide to give this a go.
Good luck!
jacknorris said:
To be honest I really don't know HTC tend to do alot of things to their ROMs so it could break things horribly for you.
Without a working services.jar the device doesn't even boot - it will just hang at the boot animation and you may never be able to restore the backup.
If you can get a copy of your ROM and place it on your device prior to testing then you could flash the ROM back over the top via CWM/TWRP to restore the original services.jar file without losing your user data.
I would be interested to hear how you get on should you decide to give this a go.
Good luck!
Click to expand...
Click to collapse
Thanks for your reply and warning.
I'll be very careful then on this topic even if I have TWRP installed and ROM backup done.
As I haven't find Android source code for my phone (except kernel code available at HTCdev.com) I was wondering if this
method could be a way to patch the existing services.jar : www(.)jordanhotmann(.)com/2011/09/android-hacking-101-compiling-and.html
(sorry I'am still not allow to post url)
Have you ever try that ?
Thx,
V.
Hello, i have a very similar goal for usb-audio. The difference is, i want to plug in a USB-Headset
when i do skype and other VoIP calles. So i want also audio input from the usb-device.
Where to find your scource?
Hi!
I'm also interested in getting usb-audio-in to work!
My usb audio device is already supported by builtin usbaudio driver kernel module and is detected by ALSA
Do you think there are any chances to get it to work without patching? AFAIK android cannot switch automatically except for 'accessory mode' usb audio events which are supported for dock stations. Maybe it is possible to change audio cards priority via config files? As far as I understand audio_policy.conf is of no use?
For those who cannot find sources: the link is in the first message, read carefully!
grandrew said:
Hi!
I'm also interested in getting usb-audio-in to work!
My usb audio device is already supported by builtin usbaudio driver kernel module and is detected by ALSA
Do you think there are any chances to get it to work without patching? AFAIK android cannot switch automatically except for 'accessory mode' usb audio events which are supported for dock stations. Maybe it is possible to change audio cards priority via config files? As far as I understand audio_policy.conf is of no use?
For those who cannot find sources: the link is in the first message, read carefully!
Click to expand...
Click to collapse
I have no idea what tools are available on android for audio stuff yet but I'm getting a nexus 7 and this looks interesting. I have some experience of doing audio stuff with linux though.
In linux, you can specify the default sound device via alsa with asound.conf or .asoundrc file. You can make relatively complex setups that will make alsa switch automatically when plugging in usb devices. the wiki:
http://alsa.opensrc.org/.asoundrc
what sort of sound related commands are available to you in android any way? Can you try these in the terminal?
aplay -l
amixer
alsamixer
aplay -l is specifically useful for determining the names of your hardware to configure alsa correctly (you should use names such as USB Audio Codec rather than HW 1,0 values).
OK well this is very interesting. I'm off to check what's been made available to android so far...
This is exactly what I am looking for. I have just got my N7, isn't even rooted yet. But I am going to try this out in a few days, and test it with the FIIO E17, which is why I bought the N7.
It will take a few days before I have access to a windows computer for the rooting, but then I will come back with my experience of it.
grandrew said:
Hi!
I'm also interested in getting usb-audio-in to work!
My usb audio device is already supported by builtin usbaudio driver kernel module and is detected by ALSA
Do you think there are any chances to get it to work without patching? AFAIK android cannot switch automatically except for 'accessory mode' usb audio events which are supported for dock stations. Maybe it is possible to change audio cards priority via config files? As far as I understand audio_policy.conf is of no use?
For those who cannot find sources: the link is in the first message, read carefully!
Click to expand...
Click to collapse
I am working on moving the code to a separate service which should allow switching to USB audio without having to patch any files you could instead install an APK, it would also be much safer than replacing the entire services file. I'm afraid that a config modification alone isn't going to make this work as there is simply no detection code to make and execute the switch.
bbop said:
I have no idea what tools are available on android for audio stuff yet but I'm getting a nexus 7 and this looks interesting. I have some experience of doing audio stuff with linux though.
In linux, you can specify the default sound device via alsa with asound.conf or .asoundrc file. You can make relatively complex setups that will make alsa switch automatically when plugging in usb devices. the wiki:
http://alsa.opensrc.org/.asoundrc
what sort of sound related commands are available to you in android any way? Can you try these in the terminal?
aplay -l
amixer
alsamixer
aplay -l is specifically useful for determining the names of your hardware to configure alsa correctly (you should use names such as USB Audio Codec rather than HW 1,0 values).
OK well this is very interesting. I'm off to check what's been made available to android so far...
Click to expand...
Click to collapse
The alsa-utils package was the first thing I tried when attempting to make this work and while it can be compiled and successfully used to play and record audio it cannot be used to make configuration changes that are respected by the Android audio system.
henrylar said:
This is exactly what I am looking for. I have just got my N7, isn't even rooted yet. But I am going to try this out in a few days, and test it with the FIIO E17, which is why I bought the N7.
It will take a few days before I have access to a windows computer for the rooting, but then I will come back with my experience of it.
Click to expand...
Click to collapse
Sounds good - let me know how it goes :good:. I have personally tested an E7 and it works fine, the E17 I believe needs to have USB charging disabled or it draws too much power.
Just a small note - I have had some people getting UI crashes after replacing the services file. As mentioned above I am working on moving things into a separate service which should solve compatibility issues across different roms.
My first initial test did not work.
What i have done: I rooted the device ( so I am in standard rom 4.2.1) installed the trinity kernel, and your two zip files ( and the trinity instead of the CM10 kernel). No sound in the FIIO yet. Is there something I have missed? Do I need to also install another ROM - I thought that the trick was the kernel.
I will be willing to test what you like, so can you give me an advice of what to try?
my next try was to install cm - I took the newest version, which apparently was a mistake. The installation went fine, but when I added the audio mod, it got stuck in the startup cm animation. Just to clarify - the CM version you are using is it a 4.2.1?
Same here:
stock rom 4.2.1
rooted;
latest trinity kernel
flashed both zips
sound either works over speakers or over usual headphone jack but not over DAC
the tested soundcard is an asus xonar u3
Thank you very much for your work. I'm highly interested in this project and a solution for my problem. If this would be implemented in CM10/AOKP it would be a great feature. Greetings from Germany
Thanks for the input.
As previously mentioned changing the entire services file is probably not the best solution as you have seen it has caused a few roms to stop responding. As for things not working entirely I am not sure yet.
I will attach the separate service soon, providing I can get it to work reliably so you can test without having to change the services file.
If that doesn't work out I will attach a build with more logging enabled so we can workout what is going on.
jacknorris said:
Thanks for the input.
As previously mentioned changing the entire services file is probably not the best solution as you have seen it has caused a few roms to stop responding. As for things not working entirely I am not sure yet.
I will attach the separate service soon, providing I can get it to work reliably so you can test without having to change the services file.
If that doesn't work out I will attach a build with more logging enabled so we can workout what is going on.
Click to expand...
Click to collapse
That sounds great. Can you say which version of android (CM) you working successful with ( 4.1.2, 4.2 or 4.2.1?).
All the best
Henry
I can really get nothing to work. I installed a 4.1.2 rom, with the appropriate trinity, modded the asound.conf, but with no sound out.
I then also tried to but the pcm.usbdac command into a newly made asound.conf in the 4.1.2 rom, also that did not work. What am I doing wrong??
Not working here either:
- M-Kernel
- 4.2.1 stock rom
- flashed both zips
USB DAC works with M-Kernel when Nexus 7 is booting with DAC connected, tested with Nuforce uDac 2 and Atoll DAC D100
Samsun S3 works on the fly, just plug in OTG and DAC and it works, remove and speaker sounds.
//Mike
fristil said:
Samsun S3 works on the fly, just plug in OTG and DAC and it works, remove and speaker sounds.
//Mike
Click to expand...
Click to collapse
But your S3 is running a Samsung ROM?
My S3 with CM10 wouldn't work with my DAC. I had to flash back to stock Jellybean to get DAC working.
I would love to get CM10 and DAC working on my S3!!!
Thanks for all your hard work. It's great to see progress on this.
I tried on my Nexus 7 running the latest Faux kernel, stock 4.2.1 ROM. I plugged in a generic USB headset, with volume controls and a power on//off button. When you first plug it in, the volume buttons actually controls the Nexus 7 volume sliders! Very cool. But when you power the headset off and back on, it loses the ability.
As mentioned in the thread, hotplugging doesn't work. When you boot up with the USB headset connected, it works great.
Hahhah, whatever you guys do... don't flash these files on a Galaxy S3 !!!
Hard bricked my phone. No display, no turn-on buzz, no download mode... nada!
Ahh well, I shoulda known better than to flash kernel files meant for an entirely different device on my S3. I just really, really wanted my S3 and CM10 to work with a DAC!
Related
STOCK ROOTED DEODEXED ROM (XXBMC4 Android 4.1.2)
You'll need to flash CWM recovery from Odin.
Download HERE
ATTENTION: I zipped the rom from CWM recovery, so....DON'T rename the image.zip before flashing
DOWNLOAD ROM (Dropbox)
DOWNLOAD ROM (Google Drive)
I also introduced a 4-way reboot
(you should install Busybox from market, since I was too lazy to add this to the rom)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download 4-way reboot (Dropbox)
Download 4-way reboot (Google Drive)
ok, wait a moment... What's the [PHONE] tag about?
Just look at this...
I enabled the SecPhone.apk in framework-res.apk.
So, before you ask me if it can make and/or receive calls I'll answer you:
NO, it doesn't. Or, at least, not now.
You can only dial USSD codes.
I really don't know if it's possible to make standard calls, since the device hasn't a GSM modem, even if I know there are some mobile operators which only work in 3G mode for exemple H3G in Italy).
I also saw some videos where people demonstrated they can make standard calls with a 3G-only modem
https://www.youtube.com/watch?v=mRF2cCFehRQ
So, making and receiving standard phone calls, even if only in 3G mode, SHOULD BE POSSIBLE.
I just don't know how to enable this functionality (pretty sure that's a modem issue)
To enable Phone app flash this through CWM
Download Phone MOD (Dropbox)
Download Phone MOD (Google Drive)
If you have any suggestion about making or receiving calls feel free to PM me, or make a post in this thread. We need some investigation!
And don't forget to press the THANKS button! :laugh:
Delux9364 said:
Download 4-way reboot (Dropbox)
Download 4-way reboot (Google Drive)
Download Phone MOD (Dropbox)
Download Phone MOD (Google Drive)
Click to expand...
Click to collapse
Edit: You may want to lighten up on the tags, I found like two more links and an extra paragraph when I ripped them out. The Google Drive link was missing the label text, too. I'm a bit nervous about flashing something when the post is that sloppy...
Delux9364 said:
STOCK ROOTED DEODEXED ROM (XXBMC4 Android 4.1.2)
You'll need to flash CWM recovery from Odin.
ATTENTION: I zipped the rom from CWM recovery, so....DON'T rename the image.zip before flashing
I also introduced a 4-way reboot
(you should install Busybox from market, since I was too lazy to add this to the rom)
ok, wait a moment... What's the [PHONE] tag about?
Just look at this...
I enabled the SecPhone.apk in framework-res.apk.
So, before you ask me if it can make and/or receive calls I'll answer you:
NO, it doesn't. Or, at least, not now.
You can only dial USSD codes.
I really don't know if it's possible to make standard calls, since the device hasn't a GSM modem, even if I know there are some mobile operators which only work in 3G mode.
I also saw some videos where people demonstrated they can make standard calls with a 3G-only modem
https://www.youtube.com/watch?v=mRF2cCFehRQ
So, making and receiving standard phone calls, even if only in 3G mode, SHOULD BE POSSIBLE.
I just don't know how to enable this functionality (pretty sure that's a modem issue)
To enable Phone app flash this through CWM
If you have any suggestion about making or receiving calls feel free to PM me, or make a post in this thread. We need some investigation!
And don't forget to press the THANKS button!
Click to expand...
Click to collapse
The original text of the post once all the tags are stripped. In case anyone was interested.
twistedumbrella said:
Edit: You may want to lighten up on the tags, I found like two more links and an extra paragraph when I ripped them out. The Google Drive link was missing the label text, too. I'm a bit nervous about flashing something when the post is that sloppy...
Click to expand...
Click to collapse
I'm sorry man, I did the entire job from a sh*tty netbook. My PC is ko. I'll fix the post once it's back
Delux9364 said:
I'm sorry man, I did the entire job from a sh*tty netbook. My PC is ko. I'll fix the post once it's back
Click to expand...
Click to collapse
4 way reboot doesn't work. Same menu, but now random reboots. Besides, the sound menu shouldn't be removed completely. I don't use it, but its good not to take stock options away.
Edit: I got the menu to come up, but I couldn't use the 4-way and phone mods together. It also made my "Just Once" and "Always" launch options "Phone" and "Headphone" with a reboot every time I tried to open the status bar drawer.
http://forum.xda-developers.com/showthread.php?t=811532
http://forum.xda-developers.com/showthread.php?t=2246535
twistedumbrella said:
4 way reboot doesn't work. Same menu, but now random reboots. Besides, the sound menu shouldn't be removed completely. I don't use it, but its good not to take stock options away.
http://forum.xda-developers.com/showthread.php?t=811532
http://forum.xda-developers.com/showthread.php?t=2246535
Click to expand...
Click to collapse
It works only with a XXBMC4 rom and you've to install busybox to make it work (as I wrote)
Delux9364 said:
It works only with a XXBMC4 rom and you've to install busybox to make it work (as I wrote)
Click to expand...
Click to collapse
I didn't install the full rom, so I still had Busybox from when I installed it the first time. Are you suggesting I install it again?
twistedumbrella said:
I didn't install the full rom, so I still had Busybox from when I installed it the first time. Are you suggesting I install it again?
Click to expand...
Click to collapse
All the mods have been tested only on the image.zip I posted. So yes, you've to install it first. Then busybox, and finally flash the 4 way reboot zip.
P.S.: any suggestions about making standard calls work?
Delux9364 said:
All the mods have been tested only on the image.zip I posted. So yes, you've to install it first. Then busybox, and finally flash the 4 way reboot zip.
P.S.: any suggestions about making standard calls work?
Click to expand...
Click to collapse
That makes no sense. I need to install the full ROM you posted, then busybox, then the mod zip, then reconfigure my entire build just to get a 4-way reboot menu? That is more work than modding my own.
P.S.: VOIP
twistedumbrella said:
That makes no sense. I need to install the full ROM you posted, then busybox, then the mod zip, then reconfigure my entire build just to get a 4-way reboot menu? That is more work than modding my own.
P.S.: VOIP
Click to expand...
Click to collapse
The thing which makes no sense is that you want to install the 4 way reboot mod without to consider you're writing in a XXBMC4 deodexed rom thread. So, if you want to make it work, you MUST be on any XXBMC4 deodexed rom.
P.S.: not everyone could afford a 3G data plan and subscribe a VOIP contract. If I enabled the phone dialer is just because I want to make standard calls, not VOIP calls.
Delux9364 said:
The thing which makes no sense is that you want to install the 4 way reboot mod without to consider you're writing in a XXBMC4 deodexed rom thread. So, if you want to make it work, you MUST be on any XXBMC4 deodexed rom.
P.S.: not everyone could afford a 3G data plan and subscribe a VOIP contract. If I enabled the phone dialer is just because I want to make standard calls, not VOIP calls.
Click to expand...
Click to collapse
What makes your version different than a stock deodexed XXBMC4 with busybox already installed?
I have the wifi only, so I don't have 3g at all and can make calls. Voip is the protocol not the service. If you don't have service, you can't make calls. Using Google Voice, you can use the standard applications, but you can't just start making calls with no service provider.
Sent from my EK-GC110 using Tapatalk 4
Enabling phone is simply replacing the false with true for has_voice in the res/values/bools.xml, but did you also change has_sms? Seems that would be equally useful, since there is an SMS over GV app, too.
I'm trying to understand what modem this thing is using. (I don't have one.)
Could someone send me a dd extraction of the the RADIO partion #10 (?) or directly from firmware extraction? It should be called modem.bin. I think there a different ways of enabling phone (calls)...
E:V:A said:
I'm trying to understand what modem this thing is using. (I don't have one.)
Could someone send me a dd extraction of the the RADIO partion #10 (?) or directly from firmware extraction? It should be called modem.bin. I think there a different ways of enabling phone (calls)...
Click to expand...
Click to collapse
Here u are, I made this flashable zip. This modem comes from GC100XXBMC4_GC100ITVBLL1_GC100XXBMC3_HOME.tar.md5 on which the rom in this thread is based.
Great! So your modem belong to the Intel XMM6260 chipset (modem + RF front-end). (The modem is X-GOLD 626, and often labeled "XG626", while the front end is SMARTi UE2 or 3.
Code:
[SIZE=2]SP6260_20.02_M1S1
...
SP6260_SUPERIOR_03.1308_DB130219 2013-Mar-18 10:53:01
GC100XXBMC3[/SIZE]
The first 4 pages of my signature thread is designated to the AT commands used in this type of modems. The firmware above, is the first new one I have looked at since Intel bought Infineon. The same info above, can be obtained by AT+XGENDATA.
Now, this is not immediately going to help you get phone functionality, but at least we'll be able to know something about the RF chipset and firmware. Depending how the reminder of the RF chips are setup, we could start speculating about what would happen if we were flashing a very similar modem firmware. (Perhaps something found in an Exynos based GT-I9300?)
^ DON'T DO THIS!
But if the Camera does support phone calls, it is not necessarily disabled in modem firmware, but rather in some NV data somewhere else, or both. This is very tricky... (At least I don't know how to read/extract and interpret XMM/Exynos NV data.)
Delux9364 said:
P.S.: not everyone could afford a 3G data plan and subscribe a VOIP contract. If I enabled the phone dialer is just because I want to make standard calls, not VOIP calls.
Click to expand...
Click to collapse
If you're saying that you wanna make GSM calls, then this whole story depend on the RF-front-end components. We're talking SAW filters and antenna switches etc. Since I'm yet to see any good high-res internal pictures of this camera, I cannot answer if these components are there.
I posted this thread long time ago asking for this.
[HW][DEV] Internal Pictures Please
PS. The YouTube video of enabling 3G calls in your OP, is for a Huawei 3G USB stick. These are normally completely different from what you have here, and thus that video doesn't mean anything, unfortunately.
E:V:A said:
If you're saying that you wanna make GSM calls, then this whole story depend on the RF-front-end components. We're talking SAW filters and antenna switches etc. Since I'm yet to see any good high-res internal pictures of this camera, I cannot answer if these components are there.
I posted this thread long time ago asking for this.
[HW][DEV] Internal Pictures Please
PS. The YouTube video of enabling 3G calls in your OP, is for a Huawei 3G USB stick. These are normally completely different from what you have here, and thus that video doesn't mean anything, unfortunately.
Click to expand...
Click to collapse
Assumably, on the 3G versions of the camera they are missing vital parts, but unless Samsung was EXTREMELY lazy and VERY generous in their hardware design, they were most likely removed in the Wifi version (GC110) and the methods are most likely stubs in both, as software is easier / no more expensive to design once and leave extra parts in. That is likely why I have the AT&T kernel installed without any issues, but all that aside, there would still need to be a way to activate service, which most carries will likely deny.
Edit: I'm not saying it would hurt to look, but its nothing to dedicate too much effort into.
E:V:A said:
Now, this is not immediately going to help you get phone functionality, but at least we'll be able to know something about the RF chipset and firmware. Depending how the reminder of the RF chips are setup, we could start speculating about what would happen if we were flashing a very similar modem firmware. (Perhaps something found in an Exynos based GT-I9300?)
^ DON'T DO THIS!
Click to expand...
Click to collapse
I already did that when I was experimenting on 4.1.1. I flashed various I9300 modem for 4.1.1 and the result was that the carrier name displayed, but I couldn't use my sim card (no sms, no internet, no calls).
I haven't already tested i9300 4.1.2 modems with this GC100 4.1.2 rom, but the result should be the same.
I read in the Galaxy Tab 10.1 forum they enabled the phone functionality flashing the I9103XXLQ3 modem over stock 4.0.4 rom. Would something like that work for us? http://forum.xda-developers.com/showthread.php?t=1875024
E:V:A said:
If you're saying that you wanna make GSM calls, then this whole story depend on the RF-front-end components. We're talking SAW filters and antenna switches etc. Since I'm yet to see any good high-res internal pictures of this camera, I cannot answer if these components are there.
Click to expand...
Click to collapse
I don't want to enable GSM calls since that means we would need a 2G modem built in the galaxy camera. And we haven't it, right?
I'm just looking at enabling standard calls on the only network we have (3G)
Delux9364 said:
I already did that when I was experimenting on 4.1.1. I flashed various I9300 modem for 4.1.1 and the result was that the carrier name displayed, but I couldn't use my sim card (no sms, no internet, no calls).
I haven't already tested i9300 4.1.2 modems with this GC100 4.1.2 rom, but the result should be the same.
I read in the Galaxy Tab 10.1 forum they enabled the phone functionality flashing the I9103XXLQ3 modem over stock 4.0.4 rom. Would something like that work for us? http://forum.xda-developers.com/showthread.php?t=1875024
I don't want to enable GSM calls since that means we would need a 2G modem built in the galaxy camera. And we haven't it, right?
I'm just looking at enabling standard calls on the only network we have (3G)
Click to expand...
Click to collapse
Nevermind, I think I have them reversed. The 100 should be the one I can mod, the 110 is wifi, and the 120 should be CDMA, which would need a software change instead of a firmware modification.
Edit: Anyway, it's going to require editing the NVRAM with a donor phone to get calling since it is a CAMERA, but I have a tutorial to get it done.
twistedumbrella said:
Nevermind, I think I have them reversed. The 100 should be the one I can mod, the 110 is wifi, and the 120 should be CDMA, which would need a software change instead of a firmware modification.
Edit: Anyway, it's going to require editing the NVRAM with a donor phone to get calling since it is a CAMERA, but I have a tutorial to get it done.
Click to expand...
Click to collapse
Did you post that tutorial anywhere? Just in case someone needs it
BEFORE DOING ANY OF THESE, KEEP IT IN MIND THAT IF YOU BRICK YOUR PHONE I'M NOT RESPONSIBLE FOR IT!!
Hi guys this is a tutorial on how to port roms for Xperia E1
Search for a phone that has the same motherboard, as the Xperia E1 MSM8210(MSM8610)
In this case, I downloaded an Andromax C2 CarbonROM
Phones with MSM8210/8610 chipset: Motorola Moto E, Andromax C2, ZTE Open C, ZTE Concord II
First you have to backup your current ROM using nandroid in the Recovery.
Without this step you won't be able to access the files which are needed to port
Not necessary to backup your ROM, but It is recommended, just in case If your E1 bootloops.
If you somehow bricked your phone, use XperiFirm to download the Stock rom and flash It.
1. Go to the PORT Rom and navigate to /system/framework/
2. Find and drop framework-res.apk to the Desktop
3. Rename the framework-res.apk to framework-res.rar (or framework-res.zip If you don't have WinRaR)
4. Open the framework-res and navigate to /res/xml/
5. Copy and paste the storage_list.xml you downloaded from here
6. Close the rar/zip and rename it to framework-res.apk and put it back to /system/framework/
7. Go tohttp://forum.xda-developers.com/xperia-j-e/general/philz-touch-recovery-xperia-e1-t2941831 and download the Recovery (If you already have it skip this step)
8. Put the boot.img in the root of the port's directory
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
9. Go to recovery and wipe cache, dalvik, media, data (everything)
10. Flash the zip
If you did it correctly, by now you should see the CM/AOSP logo
Enjoy! Hit Thanks If it was helpful!
Video tutorial: <work in progress>
Note: If the ROM won't boot, It is because the PNGs are too big for the phone, so you either need to resize them, or give up.
Or you messed something up. Re-check everything before flashing the .zip.
What's not working:
Bluetooth, GPS, Wi-Fi, VPN, everything releated to Internet; Sound
Xperia E1 Spec:
CPU: Cortex-A7 1,19GHz r0p3 (2 core)
GPU: Adreno 305 400MHz (300MHz by default)
Chipset: Qualcomm MSM8210/MSM8610
DPI: 240
Total RAM: 423mb (Physically 512mb)
You chose CM for porting ?
Where is the base ? MODIFIED RAMDISK FOR KERNEL, HAL(S), ETC !
Cm has to be build on a Linux system with source as a base.
:/
Simple Tutorial..
Sent from my D2105 using XDA Free mobile app
kaustubh.rockstar said:
You chose CM for porting ?
Where is the base ? MODIFIED RAMDISK FOR KERNEL, HAL(S), ETC !
Cm has to be build on a Linux system with source as a base.
:/
Click to expand...
Click to collapse
Yep, but If you found a phone that has similar motherboard to your device, it is easy to port stuff, but not 100% guraanted to work
Building from source is much better .. !
kaustubh.rockstar said:
Building from source is much better .. !
Click to expand...
Click to collapse
Without the source files it is impossible
Also, I'm a noob compared to you, I don't know how to begin
Oh please sir don't say like that.
wtf
Kizoky said:
Hit Thanks If it was helpful!
Click to expand...
Click to collapse
you mean : "helpful to brick the E1 phone ?"
mai77 said:
you mean : "helpful to brick the E1 phone ?"
Click to expand...
Click to collapse
Unexperienced user will brick E1 ofc
If there is any nandroid backup in the SD Card then there is no problems
@Kizoky
As far as I know, there is no nadroid available for the E1.
Also, I really think that we should make like a "dev team" and focus on working on CM11 (CM12?) for the E1.
It's not impossible, but WILL take a lot of time and work.
Hell, I'm in.
zeteny.nagy.20 said:
@Kizoky
As far as I know, there is no nadroid available for the E1.
Also, I really think that we should make like a "dev team" and focus on working on CM11 (CM12?) for the E1.
It's not impossible, but WILL take a lot of time and work.
Hell, I'm in.
Click to expand...
Click to collapse
There is Nandroid for the Xperia E1, it's the part of CWM. And it is working, it just needs more than 2 GB available space on SD card. Also, none of the developers have this phone and I don't think they will ever consider buying it just to develop CyanogenMod for it. If we could get a display driver for the E1 that works (Adreno 305 or whatever the E1 has) we could compile CM, according to Kizoky. Or maybe if we could get drivers working on the ROM that has been ported from the Andromax C2's CM. We tried, I managed to get sound working, but no WiFi or Service or anything. Otherwise, it was waaaay more smoother than stock... If we could get CyanogenMod 12 even if it's broken I'm sure I would get it even without WiFi or Service, I don't care. If I will get an 8GB SD card I will attempt to get things working on this CM11, as I found new files that may be able to get WiFi working. Also an interesting note, the stock kernel that comes with the stock firmware is working with this CyanogenMod, which also means that it's possible to get CM on Locked Bootloader and it may also be possible on other devices. It's really handy, especially because I cannot unlock my BL because it is from a career. Oh my that's a long message lol
xezrunner said:
There is Nandroid for the Xperia E1, it's the part of CWM. And it is working, it just needs more than 2 GB available space on SD card. Also, none of the developers have this phone and I don't think they will ever consider buying it just to develop CyanogenMod for it. If we could get a display driver for the E1 that works (Adreno 305 or whatever the E1 has) we could compile CM, according to Kizoky. Or maybe if we could get drivers working on the ROM that has been ported from the Andromax C2's CM. We tried, I managed to get sound working, but no WiFi or Service or anything. Otherwise, it was waaaay more smoother than stock... If we could get CyanogenMod 12 even if it's broken I'm sure I would get it even without WiFi or Service, I don't care. If I will get an 8GB SD card I will attempt to get things working on this CM11, as I found new files that may be able to get WiFi working. Also an interesting note, the stock kernel that comes with the stock firmware is working with this CyanogenMod, which also means that it's possible to get CM on Locked Bootloader and it may also be possible on other devices. It's really handy, especially because I cannot unlock my BL because it is from a career. Oh my that's a long message lol
Click to expand...
Click to collapse
That was a fast reply
So the thing is that the E1 uses the Adreno 302, exactly the same as the Moto E. Which means there are drivers floating around in the CM11 builds for the Moto E. It uses the same connection boards, too - DRIVERS EVERYWHERE.
Only if I had the knowledge to do all this alone, the thing is that I can't
EDIT: Could you give me a link for CWM? I only found Philz Touch and I don't really like that, I prefer CWM
zeteny.nagy.20 said:
@Kizoky
As far as I know, there is no nadroid available for the E1.
Also, I really think that we should make like a "dev team" and focus on working on CM11 (CM12?) for the E1.
It's not impossible, but WILL take a lot of time and work.
Hell, I'm in.
Click to expand...
Click to collapse
There is. There's already a recovery for E1, which has built-in Nandroid backup, available to use.
@Kizoky
I'm going to dig around in Moto E CM11 files, maybe I can extract some display drivers.
@Kizoky
I managed to get some Qualcomm-made .APK-s from various ROMs. Does that help at all?
zeteny.nagy.20 said:
@Kizoky
I managed to get some Qualcomm-made .APK-s from various ROMs. Does that help at all?
Click to expand...
Click to collapse
I don't think they would, but maybe they do. (maybe one of them manages WiFI connectivity) Try to install them onto CM and see what happens (reboot too)
xezrunner said:
I don't think they would, but maybe they do. (maybe one of them manages WiFI connectivity) Try to install them onto CM and see what happens (reboot too)
Click to expand...
Click to collapse
I managed to get GPS / Location services up and running. There are still tons of .APK-s that I haven't tried yet.
EDIT: I think I found the WiFi driver.
EDIT 2: @Kizoky Did you check the ROM made by @ramdanzs ? It probably contains the display drivers you needed.
EDIT 3: I managed to get telephony working but now it doesn't function.
zeteny.nagy.20 said:
I managed to get GPS / Location services up and running. There are still tons of .APK-s that I haven't tried yet.
EDIT: I think I found the WiFi driver.
EDIT 2: @Kizoky Did you check the ROM made by @ramdanzs ? It probably contains the display drivers you needed.
EDIT 3: I managed to get telephony working but now it doesn't function.
Click to expand...
Click to collapse
Wi-Fi and Bluetooth? Those 2 bastards that are always idling and don't do anything at all.
zeteny.nagy.20 said:
I managed to get GPS / Location services up and running. There are still tons of .APK-s that I haven't tried yet.
EDIT: I think I found the WiFi driver.
EDIT 2: @Kizoky Did you check the ROM made by @ramdanzs ? It probably contains the display drivers you needed.
EDIT 3: I managed to get telephony working but now it doesn't function.
Click to expand...
Click to collapse
If you get any drivers working, please let us know immidiately.
xezrunner said:
If you get any drivers working, please let us know immidiately.
Click to expand...
Click to collapse
Told ya, GPS is fine
---------- Post added at 05:50 PM ---------- Previous post was at 04:51 PM ----------
@Kizoky
I just found this tool called FTF Extractor can be used to decompress .FTF firmware files of Sony Xperia phones, just as listed in this article/tutorial on how to decompile .FTF files.
Is it possible to grab some drivers from the stock firmware and port it to CM11? Just askin'.
AFAIK .FTF files are just "renamed" flashable .zips so, their structure is the same.
AOSP 5.0.2 Barebones for D2303
Hi all.
This is my first run of compiling a barebones AOSP 5.0.2 for our D2303's. I got sick of all the failed ports and wanted to make my own from scratch. Here you have my first launch. You can not get as barebones as this. This ROM was made using the guides on Sony Developer website and should be the same result if anybody else follows the same steps.
I have made ZERO modifications to this ROM. I have changed no code, made no patches or even themed it with a custom name. This ROM is as-is if you built it following the same guides on Sony's site. I just saved you the time.
**This ROM works!**
Data / Calls / SMS / NFC / Bluetooth / GPS/GloNAS / Wifi all work!
Camera does not. It might, but I broke mine and doesn't even work after stock restore!
No lag!
Clean, basic, no-frills, xPosed ready!
Unlock your bootloader!
Be running either a modem from a 4.4.2 ROM or a 4.3 ROM!
This ROM is provided as-is. The sources are freely availble following Sony's guides. You use it purely at you own risk!
Let's clear some confusion with this device, which I am shocked top developers have missed!
* You **have* to be running either 4.3 or 4.4.2 MODEM! If you are running a 4.4.4 ROM, use Flashtool to drop back to 4.4.2 or 4.3 first
* You will not be able to boot ANY 5.x ROM with a 4.4.4 modem, it **HAS** to be 4.4.2 or 4.3 MODEM!
There are guides on how to revert back on this forum and I will not detail that here. But in essence, it is only the modem you need to revert back.
This ROM I would say is usable.
* Camera doesn't work on mine, but I broke it to the point it wont work in stock ROM
* Calls / SMS / Data / Wifi / GPS / NFC / Bluetooth all appear to work as they should
* Sensors appear to all be working as they should (at least compass and light)
* No lag or FCs
This is a totally unmodified ROM using the AOSP & Sony sources provided in Sony guides. I did not develop or make any of the code or scripts. I simply compiled it, flashed it and now using it. All credit to the software that made this ROM goes to all those involved in making, patching and taking the time to make this work.
I do not want any donations. If you wish to donate, donate to FXP/CM12/Omni/PAC/TWRP and the persons that created what I have simply bundled here.
Download via magnet/bittorrent only for now. For trackers, please use OBT trackers. Issue with previous download! I somehow crossed an .img from another project as the boot.img for this. I have recitified this issue and the correct boot.img has been added. Apologies for this & thankyou to all whom spotted it.
Magnet Link
magnet:?xt=urn:btih:44d710f71b92adb9e64475994b5ab905d665af7d&dn=AOSP-5.0.2-D2303.tgz&tr=udp%3A%2F%2Fopen.demonii.com%3A1337
Mega Link
https://mega.co.nz/#!HZUUCCJS!AgjmKr4Nx4NMWPKxVXIGfp72m9JyMMlsF0pvzuGBrg8
Sorry for the bad link effort, since I am new to contributions I'm stuck until I make the relevant posts.
I have no idea if this will work on any of the variants of this device. You are welcome to try, but don't blame me if you break it. This ROM comes as is, is provided under the same licenses as AOSP and Sony Development.
Tricks & Tips:
* Download the .zip for Omni ROM 4.4.4 for our D2303's. Extract the boot.img and keep it safe. This boot.img holds a reliable TWRP which we can use to ''fastboot boot'' instead of flash and even make a reliable backup of a stock ROM. When you put device into fastboot/bootloader (hold power up when plug in data ready cable), execute ''fastboot boot boot.img'' which will boot that kernel w/o modifiying anything. Now keep hitting volume down when you see Sony logo. TWRP should load!
* Use this for all your backing up, flashing zips, ROMs etc. Do NOT flash it. Just fastboot boot it instead. This can even be used AFTER we install Lollipop for the same reasons.
* Flashing this ROM requires you to use the above TWRP to wipe all partitions, System, Data, Cache etc. It's best to start afresh (I actually wiped everything except since I wanted a totally clean slate, wiping external storage isn't necessary but wiping internal is recommended.)
* Extract the tarball with the .img files
* Put the device into fastboot mode again!
* execute the following commands:
* fastboot flash boot boot.img
* fastboot flash system system.img
* fastboot flash userdata userdata.img
Make sure all processes complete successfully!
Unplug cable, wait a second or two and power up your device! (I prefer this to fastboot reboot as the data cable can hang the device in a weird, red led stays on mode that has bootlooped me a few times).
Give it a while to boot. Whalla, Lollipop!
If you want gapps, using the fastboot boot method above with our Omni 4.4.4 boot.img and TWRP.. Download CM's gapps for Lollipop and flash/install it. This does not lag the device. However, you will get a black screen for a while after first boot of installing any system/ZIP flashable (it wont show updating apps, just blank screen). BE PATIENT! The same applies if you do anything that triggers that "Updating App X of X.." Android is updating effort.
xPosed requires you to follow the instructions for flashing the ZIP then installing APK. Use the same method above for installing the ZIP.
To get root, just download the latest SuperSU-2.x.zip and flash the same way as above.
**Issues**
* With a 4.3 Modem, the Bluetooth is slow coming to life. Take about 5 mins when turned on from off. 4.4.2 modem doesn't seem to have this issue
* Location services will forget a change to Accurate on a 4.3 Modem. On 4.4.2 Modem doesn't seem to do this.
* My loudspeaker during calls is tempremental, sometimes it works sometimes it doesn't.
* Some OTG devices work, some dont. I had one or two pendrives that did, some that didn't & a 3G modem (with PPP widget's help) that did & another that didn't!
* Screencasting initially didn't work. Enabling Developer Mode and disable HDCP checks seemed to allow some functionality for me.
* Data icon always said 3G for me, even when on HSPA(+) - I use OSM which showed varying network types. GPRS/EDGE shows as 2G. I do not know for 4G as my carrier isn't 4G enabled yet.
* No hardware accelleration (using VLC & MX Player as guides) for video playback, however it can playback a 1080 MKV over wifi no problem.
* Same applies to screen-recording software. I can't seem to get native Lollipop one to work at all, but SCR Free works.
* 3D Performance is a little smoother than in stock ROM (IMPO playing Ingress).
* GravityBox for Lollipop works. However!! On some instances it can cause a softboot on a boot up (when it goes for PIN entry). For me it comes back after they next cycle. Not pinned it down to what in GB doing it though.
* Compass, proximity & light sensors all work. There is some screen flicker once so often when using dynamic brightness.
* No way to force use of 5Ghz or 2.4Ghz wifi (or leave it to select auto) as there is in stock ROM.
* Battery life when using the device as I do is as the same as stock, the device is however faster in general. I can sit it for 29 hours idling, providing not too many calls. The powersaving modes built-in can extend on this but I haven't properly tested.
I only mention these as some people may care to know. If the camera worked, I would actually be totally happy with this ROM minus it's few pitfalls.
MD5's for the paranoid:
2c053445ab096e813afc2a02079aba85 boot.img
af636c1558e8d6651f211dbd2042443f system.img
adbb0b8d0b5eee98186a71a00d8352a4 userdata.img
Good job, please, compile an AOSP 4.4.4
Sent from my D2303 using XDA Free mobile app
What if I told you I did the same as you and it is EXACTLY the same build you can find on FXP's blog (but files are not straight uploaded, so build can be a little bit outdated). Developers around here are working on sources, and changes are on Xperia Developers Github.
As you can see there are things jerpelea (FXP) has pushed.
https://github.com/sonyxperiadev/device-sony-eagle
Only untouched sources are for Nexus, all other devices need to be patched, and sometimes rewritten from scratch (for example camera wrapper).
If I install this rom, and when I back to stock rom, i won't be able to use camera?
Is that right?
Um ok but why there is no seeding?;/ and why dont u give an alternative link?? haw we supposed to try this rom mate?
who can confirm if camera works or not ?
Update
I will work on a 4.4.4 AOSP eventually. Thanks for the tip, I'd also be curious on this.
I do not doubt that developers that are working on Omni/PAC/CM/FXP have submitted code, that's probably why the barebones is working sweet. I did try FXP but ran into different issues on different versions (all already documented). I built this on a whim as I just got fed up.
With the camera, that is exactly how I killed mine, and I also lost the original backup I made with Flashtool/Companion as well as from TWRP. So I have no hope. If you keep/make a backup upon successful bootloader unlock (companion/flashtool), you should be OK if you do a stock revert that is documented on this forum.
For the download link, sorry about this. I used transmission and it went into meltdown last night from another seed. I believe mega is a method people use here, is there any other suggestions. I will do this when I get back home and check back here.
** I am uploading this to Mega now, I will add the download link to the OP. **
Thank you for uploading this rom Dutch.
I ll test this rom, correct it where i can and send you pm as soon as possible with some fixes plus solution about your camera
cross your fingers to not break mine lol
Best regards
Vampirian
Thanks
If you do make some patches, can you please put them as flashable ZIPs? I really don't want to go and start tampering with a somewhat stable base. I bless whoever made that boot.img for the Omni 4.4.4 - I would like to try and get that working here, but again tampering.. Just means needing a PC or tablet to make mods to your phone each time.
I may have a bash at a custom kernel with a recovery for this, but I'm not rushing into that idea just yet.
** Update **
I got curious about the FOTA partition I saw using Flashtool and see there are already ports of custom recoveries (with custom boot kernels with elf extract support). I am overly curious about this now as I would love to have this TWRP from Omni's boot.img for my internal recovery. I have already made a custom kernel for my device and it seems to not effect anything (not changed a thing mind). I may now start to tinker!!
Has anybody tested this rom?
---------- Post added at 03:37 PM ---------- Previous post was at 02:53 PM ----------
I have the problem with boot.img
It says, failed: this is not a boot image
Bug list same as the omni one
Can You explain that boot.img is over 400MB Large!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Which download did you use? That is so not right!! boot. img should only be about 6/7 mb. are the md5s matching on system and userdata? i will look into this asap
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
The mega download is shot. It has become corrupted and I will remove the link from the OP. DO NOT USE IT!
The magnet link is still fine and extracts properly.. Just be patient as there are only 3 peers at present.
I am still using this ROM and there are some issues.
I failed to get Wifi tethering to actually route. It would run, give dhcp and even resolve DNS, but it is as-if the the nat forwarding rule has been missed and everything blackholes.
Camera is a total no go for me, I fooked mine in other ways though.
For how I use my phone (calls/sms/Ingress/HO/G+/Whatsapp/Maps/Wifi location mapping (OSM/Mozilla stumbler/Wigle) / Skymaps) it does just fine. Battery life isnt impressive vs. stock overall (doing same as above). xPosed allows tweaking, but this is where instability occurs.
GB works quite well, but avoid things that dont have direct L support (xPrivacy/Lightningwall etc.).
What I want to do is submit my phone into submission and try to get my camera working in a stock again, then give this another bash. It is a usable ROM if you just want a clean fast phone with no thrills (or camera).
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Magnet link not working
The magnet link you posted doesn't seem to work for me. I get "unable to parse magnet URI!" error
There is a space in the magnet part of the URI when you C&P. The forum did this. I should be able to post proper links soon.
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Nice for giving so much info on AOSP experiences and "prerequisites" (like 4.4.2).
I'm using a AOSP 5.1 build I made myself, and have to say the only issue with the latest build/kernel is battery drain (and camera, but "they" are working on it).
I Hope nobody will call you a troll because you share your builds and experiences with everybody
I got a massive lag when using browser or while using a few apps at once, also installing apps and turning on bluetooth take alot more time.
The things I do like is that it is pretty stable....
Thanks to all that have and are testing.
The tether issue was my tablets fault and does actually work. As does BT tethering.
All of the sensors work (i went out of my way to try each one (magnet sensors are always fun)).
The slow Bluetooth I found only happens when using a 4.3 modem. I dont get it now using a 4.4.2 modem.
There is no call record ability in this ROM. CM11/12 have enabled this feature, I believe its a small. xml patch, can anyone confirm please?
I do experience slowness with lots of open apps, i also notice if you have a lot in frequents its a pain to clear all (fixed with gravitybox mind). They also seem to come back even after a reboot. I do find myself regularly clearing the frequents which does sort it.
And thanks for the tips. I find trolls arent entirely too common here. Ive been reading from XDA for years and my sole idea was to demonstrate that its is doable and quite easy. I am still using this ROM everyday and Im quite happy with it. I do still prefer Kitkat though
I do want to play with 5.1.x (and nicer the camera works) - but i went 5.0.2 simply because of xposed support. Nothing else
There is a battery drain which I noticed "out-of-the-box" so to speak. This happens when there are issues with "qdoverlay" which i noticed sometimes occurs on bootup, then will savage your cpu. I spotted this in logcat and didnt find a direct fix (other than sleep the screen when the phone starts lagging, wait a second or two then wake it back up. Location type also counts, oddly high precision seems to give me more life. However, there is an "Over-Counted" cropping up in battery stats, which I cant pin is for what, as its usually a high figure at the bottom.
Can anyone confirm a working camera on this ROM? Opencamera or Googles should work if one doesnt show up.
Thanks again everyone
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Dutch Burdock said:
Thanks to all that have and are testing.
The tether issue was my tablets fault and does actually work. As does BT tethering.
All of the sensors work (i went out of my way to try each one (magnet sensors are always fun)).
The slow Bluetooth I found only happens when using a 4.3 modem. I dont get it now using a 4.4.2 modem.
There is no call record ability in this ROM. CM11/12 have enabled this feature, I believe its a small. xml patch, can anyone confirm please?
I do experience slowness with lots of open apps, i also notice if you have a lot in frequents its a pain to clear all (fixed with gravitybox mind). They also seem to come back even after a reboot. I do find myself regularly clearing the frequents which does sort it.
And thanks for the tips. I find trolls arent entirely too common here. Ive been reading from XDA for years and my sole idea was to demonstrate that its is doable and quite easy. I am still using this ROM everyday and Im quite happy with it. I do still prefer Kitkat though
I do want to play with 5.1.x (and nicer the camera works) - but i went 5.0.2 simply because of xposed support. Nothing else
There is a battery drain which I noticed "out-of-the-box" so to speak. This happens when there are issues with "qdoverlay" which i noticed sometimes occurs on bootup, then will savage your cpu. I spotted this in logcat and didnt find a direct fix (other than sleep the screen when the phone starts lagging, wait a second or two then wake it back up. Location type also counts, oddly high precision seems to give me more life. However, there is an "Over-Counted" cropping up in battery stats, which I cant pin is for what, as its usually a high figure at the bottom.
Can anyone confirm a working camera on this ROM? Opencamera or Googles should work if one doesnt show up.
Thanks again everyone
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Click to expand...
Click to collapse
Camera is not working
Dang. Thank you.
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.
ROMs with Bluetooth Fix!
For several years I have been frustrated with CM and LOS being unable to connect to my car. To compound this, most custom ROMs are based on these ROMs and use the same BT stack making it nearly impossible to find a custom ROM that works with my vehicle. I had assumed that it was hardware driver related until I found that it happened with the Oneplus 3T as well. I was beginning to lose hope.
But thankfully, it turns out that AOSPA uses a different BT stack that actually works with my car, so I spent several weeks researching ROM building and was finally able to build my favorite ROMs with AOSPA's BT stack! I have made a flashable zip using a bluetooth file found in the stock ROM to fix the issues I've been having. The zip is below. If you have a different device and would like this fix feel free to pm me to make a zip or just follow the instructions in post 2 for how to apply the fix in TWRP without a zip.
Disclaimers:
-I only have a Oneplus 3T, not a 3. This zip should work on both, but keep this in mind.
-This will only fix the issues you're having if the ROM you're taking the file from has Bluetooth that works.
BT Fix v1.2
XDA:DevDB Information
[LOS][RR][GZR] Bluetooth Fix for Existing ROMs, ROM for the OnePlus 3
Contributors
shadeau, TheCrazyLex, Thecrazyskull, arter97, xboxfanj, chrislahaye, carlosavignano, arzbhatia, scoobyjenkins, martinusbe, otisman, akhilnarang, varund7726, westcrip
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: OOS 4.1.6 or later
Based On: AOSP, LineageOS
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2017-09-20
Created 2017-06-21
Last Updated 2017-11-21
Manual Bluetooth File Replacement Instructions
1) Install the ROM with working bluetooth on your device in TWRP
2) While in TWRP (no need to boot) mount the /system folder
3) Using the file manager navigate to /system/lib/hw, select the bluetooth.default.so file, and tap copy
4) Paste this file somewhere in the base /sdcard directory where it won't be deleted when you factory reset
5) Install your favorite ROM with everything like you normally would/restore it from a backup
6) Mount /system in TWRP again (if it became unchecked or you rebooted)
7) Use the file manager to locate the bluetooth.default.so file that you just placed in your internal memory
8) Copy the file and paste it in /system/lib/hw
9) Reboot and test by connecting to device
10) Enjoy!
Troubleshooting
The flashable zip basically does three things:
1) mounts system partition
2) copies modified bluetooth file to system partition
3) unmounts system partition
4) performs update script like all zips
The zip assumes that your system partition is in the normal location (for a 3T) and formatted in ext4 for my script to work. If you have issues then try manually mounting the system partition with TWRP before flashing the zip.
Reserved2
Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Edit: Nevermind. I misunderstood what this was. Still, thank you very much! I cannot wait to try it still!
jbw716 said:
Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Click to expand...
Click to collapse
I've built full ROM zips, so you'll need to do a clean install of the ROM that you prefer and you should be good to go. Hope that helps.
Superbbbbbb Thanks, waiting for this fixing for a long time. BT with gear s.3 WORK. Please be keep update.
BTW RR Roms from your file why option in notification slider in additional buttons are difference from the link thread
Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!
plepew said:
Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!
Click to expand...
Click to collapse
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
shadeau said:
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Yes, a flashable zip would be the way to go if possible.
I will try Validus on the weekend and report back if I have success... I've installed in in the past and it's nice. But prefer Tesla due to some features.
Thanks for the quick response!
Cheers!!
shadeau said:
I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Should be doable unless framework is involved.
silentvisitor said:
Should be doable unless framework is involved.
Click to expand...
Click to collapse
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!
Would you be open to posting your sources for these builds?
Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.
Excellent job brother! I too have the same issue with my 2015 Nissan Altima. I honestly have no idea why the makers of these roms don't just use this BT stack...... OOS has no issues with my car, so why don't they all use OOS BT? Just makes no sense to me lol
jbw716 said:
Would you be open to posting your sources for these builds?
Click to expand...
Click to collapse
I'm totally open to that. But I need to figure it how to post to git first .
jbw716 said:
Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.
Click to expand...
Click to collapse
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.
shadeau said:
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!
Click to expand...
Click to collapse
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).
shadeau said:
I'm totally open to that. But I need to figure it how to post to git first .
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.
Click to expand...
Click to collapse
Here you go. I hope it helps!
https://drive.google.com/file/d/0B22KzlQ3gJRaMHhNbGVDd29JMXM/view?usp=drivesdk
silentvisitor said:
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).
Click to expand...
Click to collapse
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.
shadeau said:
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.
Click to expand...
Click to collapse
Search for "bt" and "bluetooth" in both folders and you'll get list of files. Now extract those files, make a flashable zip and test with some other ROM
Unfortunately the hoster where my build server is located raised the fees and i had no way to download a backup of my data... As i can't afford it now i had to delete everything. With a heavy heart I have to discontinue this great ROM for a great phone..
- first of all, thanks to @tdm for his tremendous effort to have us all enjoy LineageOS in the first place, without his contribution this thread would never exist. Also thanks for tdm's Lineage 14.1 where I took this post's layout from -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gentlemen,
The time has come to share what's due to be shared.
Supported devices
* US model running 7.1.1 b14 firmware
* EU model running 7.1.1 b12 firmware
Pre-requisites
Make sure to have at least this TWRP version installed
Patience as first start takes a while
First time install Instructions
Use these instructions when coming from any other ROM (stock, AOKP, LineageOS 15.1, etc.)
Download ROM.
Download GAPPS if desired.
Boot into recovery.
Backup your current data.
Format/Wipe 'Dalvik/ART Cache', 'System', 'Data' and 'Cache'
Flash ROM.
Flash GAPPS if desired.
Reboot.
Upgrade instructions
Use these instructions when upgrading from a previous Lineage 16.0 build.
Download ROM.
Boot into recovery.
Backup your current data.
Flash ROM.
Reboot.
Flashing instructions
There are two main ways to flash files onto your phone: local and sideload. Most people are only familiar with local, but sideload is much quicker and easier if you are at a PC.
Sideload
Download the ZIP file(s) to your PC. In TWRP, select advanced and then sideload. Swipe the slider to begin, then on your PC run "adb sideload <filename>".
Local
Download and/or copy the ZIP file(s) to your phone. Note whether they are on internal storage (the default) or the sdcard. In TWRP, select install, find your file, and select it.
Status
This is currently stable quality
Known issues
Very minor graphical glitches
sometimes videos don't play, you have to remove the relevant all from your recent app list and restart (e.g. WhatsApp)
AKM DAC is not supported
Selinux permissive
To Do list
Implement Camera2 API Thanks for customizing libraries and not sharing any code or insight ZTE
Get DSP to kick in for high quality audio again
Download
Google Drive
* works well with open gapps
Sources
Device tree
Kernel
Vendor
Note: please refrain from requesting other Android distributions from me, like AOKP, AOSP, etc - this is most likely not going to happen from my end. As I provided all my sources you can fork the stuff yourself and try to build
Special thanks
@R3bornD4rth for having provided me an axon 7 mini for my testing/debugging, which is heavily in use and doing great so far
@tdm for his original work on this
@armandop_ for his ZMAX Pro Repo and help getting LiveDisplay to work (flawlessly, thanks mate)
intervigilium aka Ethan Chen for his work on HTC One A9 (hiae) (which shares the same chipset as our phones)
Thanks for this rom, there's a way to make work the camera API 2 (in the future)?
jose_777.mx said:
Thanks for this rom, there's a way to make work the camera API 2 (in the future)?
Click to expand...
Click to collapse
Good question, no clue if I will be making it to work somehow I can try to get some pointers if there are just some drivers to be altered or whatever is needed to have this done
I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!
bius88 said:
I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!
Click to expand...
Click to collapse
Cool!
Would be better if GPS and Cam would work though I am working on GPS right now, will soon test my latest build, so fingers crossed
Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks
Holyoblation said:
Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks
Click to expand...
Click to collapse
What? The camera really works? Then I shall replace the camera app with another one maybe ?
Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.
koktey14 said:
Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.
Click to expand...
Click to collapse
I see 2 issues here to be fixed. first with the video playing will be added to my known bugs post, the flashlight thing is related to the camera not working (pretty sure at least)
Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now
TheSSJ said:
Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now
Click to expand...
Click to collapse
Can there be a chain problem with sim card, graphics or camera maybe
koktey14 said:
Can there be a chain problem with sim card, graphics or camera maybe
Click to expand...
Click to collapse
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)
TheSSJ said:
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)
Click to expand...
Click to collapse
Apparently I fixed wifi I rebooted 15 times to be sure and it always turned on, GPS still functioning as well!
I will update the OP and proceed with cam (which is so broken that not even 3rd party apps work at the moment)
EDIT: Notification lights fixed as well
@TheSSJ -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?
Hi, thanks for the hard work. Does the firmware support fast charging?
BAPK said:
Hi, thanks for the hard work. Does the firmware support fast charging?
Click to expand...
Click to collapse
Yes, as this is setup on kernel side the stock settings have been just kept
k500zm;79544339 [user=2388665 said:
@TheSSJ[/user] -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?
Click to expand...
Click to collapse
Twrp is the same with oreo i installed it.
I was thinking about aokp too but didnt want to put pressure on you. you are already busy. @TheSSJ what do you think about this?
Once I fixed all issues with LOS16, compiling aokp should not be too hard, but I can't promise it
Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.
koktey14 said:
Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.
Click to expand...
Click to collapse
Strange,i just clean installed and it is working really fast
Can you provide dmesg and logcat please, then I can check