[ROM] [UNOFFICIAL] CyanogenMod 10.1 - Android 4.2 WIP
- Thread starter madmack
- Start date
-
- Tags
- development
- Status
Solid explorer sdcard1 is what's linked via extsdcard and I'm getting 775 perm. Card is formated to FAT32 put it in while booted, rebooted into recovery and flashed ur cm10 on top itself (already running ur cm10) wiped cache/dalvick rebooted and got nothing...pulled SD card, it booted, put SD card back in and then pulled SD card, system yelled at me that SD card has been removed...put it back in and rebooted and stuck on boot animation...pulled SD card and it finishes boot...idk its frustrating because I know its not the card, and because you don't have the issue lol...suppose for a moment you have the issue what could I provide to maybe show you what I'm talking about...my last resort is to do a full system wipe and reinstall to see if that fixes it, but that's last ditch.
Also in relation to the security exploit, I downloaded supercuiro's voodoo app and it says that I am vulnerable...I will be applying the fix shortly to figure out if it breaks camera and go from there. It also seems that cm10.1 merged the fix into their repos already so you shouldn't have to worry about it going forward.
Edit: quick fix does not break camera for me...now I'm disabling quick fix and enabling fix at boot.
Edit 2: enabled fix at boot and it does not break camera and fixes exploit.
Sent from my SGH-I317 using xda app-developers app
Last edited:
The note is is vulnerable. I applied Chainfires fix and it does not kill the camera on CM.
Cool so both chainfire and supercurios apps fix this exploit and won't break the camera for all who are concerned and want to fix the exploit...also for the newer member this does not remove root access it just fixes an app bypassing asking for root access rights...meaning when you select titanium back up for the first time either superuser or super su ask u to allow root access or not that is the correct way for that to happen...the I exploit allows apps the bypass that question and allow the app root access and it can then pull everything stored in RAM memory...what's stored in RAM I'm not sure and I hope someone who knows chimes in...but both fixes out there work and will not break camera for cm10
Sent from my SGH-I317 using xda app-developers app
Bad news regarding the audio ril scene.
As I suspected, audio.primary.smdk4x12 does not do anything with libsecril-client. This is what makes our devices so different than all the Exynos GSM (non LTE) variants of the S3 and Note 2. This means that the source code under hardware/samsung is basically useless for us.
What does it use instead? It interfaces with libaudio-ril.so which in turn calls some functions in libcsd-client.so. libcsd-client then talks to our RIL qualcomm libraries and sets up the proper voice path. The closest thing we have is Google's own Qualcomm ALSA implementation that exists in hardware/qcom/audio. Google themselves are symlinking functions to libcsd-client at runtime so we know for certain that libcsd-client is a qualcomm proprietary and is closed source.
Wait, maybe libaudio-ril is so similar to the other phone's libsecril-client? Nope. Looking at the symbols the library provides, it has really nothing to do with libsecril-client:
dyanmic symbol table from libaudio-ril.so:
and libcsd-client.so: (google calls functions like csd_client_start_voice explicitly.
I was thinking we could skip libaudio-ril.so all together and call functions in libcsd-client just like google does. Problem is, the audio libcsd functions are made for qualcomm based chipsets and Samsung does mash-up functions from their own exynos alsa implementation (for everything except ril) and some functiosn via libaudio-ril.so to interact with qualcomm's stuff. Unfortunately trying to guess what exactly is happening: which functions are being called, what is the function signature exactly (parameters, return values) and in what order are they called is nearly impossible. We can try abandoning the entire exynos audio implementation and pretend to be qualcomm. Basically that will give us the qualcomm libraries that google uses for the nexus 4 for example but I highly doubt that this will even work given the very different hardware so I didn't pursue that path.
How to fix this?
1. Get the sources for the library (audio.primary.smdk4x12) that we use from Samsung. After all, the other exynos GSM phones do have that library open sourced somehow although it is not applicable or complete for us. I'm not sure who to contact about that.
2. Some genius reverse engineers audio.primary to figure out what exactly is going on. This is time consuming and is way beyond my league.
3. Mix the exynos audio.primary with the qualcomm audio.primary to try and get things rolling. To me though, the odds of getting this working are very slim. You'll be shooting in the dark. Maybe someone is more capable of disecting the library and have some more educated guesses as to what is going on.
4. Wait until Samsung releases 4.2 for any exynos + qualcomm lte phone. We can then use the libraries without knowing what exactly happens behind the scenes just like what we currently have in CM10.
I understand the community's frustration at samsung's lack of documentation and source.
Two things I already tried as well just in case someone wants to try them: 1. Backport the HAL JB library. It eventually crashed due to API compatability. I overrode the explicit checks and that led to SIGFAULTs in mediaserver. 2. symlink and call functions in libaudio-ril.so instead of libsecril-client.so from our audio.primary.smdk4x12 sources. Didn't work. CSD library wasn't getting the correct voice path and I have no idea what API it uses or what it expects. I can elaborate more if someone is interested.
you're not able to boot at all with that sdcard? if the thing is stuck at the boot screen, you can logcat it and put it in pastebin so I can have a look. these issues are usually easy to solve once you got the logcat setup properly. (enable debugging in dev, install the sdk. use adb from terminal or cmd while the phone is connected via usb and bootlooping).
everything currently running in your phone is stored in ram
As I suspected, audio.primary.smdk4x12 does not do anything with libsecril-client. This is what makes our devices so different than all the Exynos GSM (non LTE) variants of the S3 and Note 2. This means that the source code under hardware/samsung is basically useless for us.
What does it use instead? It interfaces with libaudio-ril.so which in turn calls some functions in libcsd-client.so. libcsd-client then talks to our RIL qualcomm libraries and sets up the proper voice path. The closest thing we have is Google's own Qualcomm ALSA implementation that exists in hardware/qcom/audio. Google themselves are symlinking functions to libcsd-client at runtime so we know for certain that libcsd-client is a qualcomm proprietary and is closed source.
Wait, maybe libaudio-ril is so similar to the other phone's libsecril-client? Nope. Looking at the symbols the library provides, it has really nothing to do with libsecril-client:
dyanmic symbol table from libaudio-ril.so:
Code:
DYNAMIC SYMBOL TABLE:
00002d80 w DO .data.rel.ro 00000064 _ZTVN7android8AudioRilE
00000000 DF *UND* 00000000 __aeabi_unwind_cpp_pr0
0000105d g DF .text 00000004 _ZN7android6QmiCsd4initEv
0000105d g DF .text 00000004 _ZN7android6QmiCsd5closeEv
0000105d g DF .text 00000004 _ZN7android6QmiCsd15checkConnectionEv
00001067 g DF .text 00000002 _ZN7android6QmiCsd16setVoiceSolutionEv
0000106d g DF .text 00000004 _ZN7android6QmiCsd14setExtraVolumeEb
00001071 g DF .text 00000024 _ZN7android6QmiCsd14setScoSolutionEbi
00001095 g DF .text 0000000a _ZN7android6QmiCsd14closeVoicePathEii
00000000 DF *UND* 00000000 __aeabi_unwind_cpp_pr1
0000109f g DF .text 0000000a _ZN7android6QmiCsd15isLoopbackStartEv
000010a9 g DF .text 000000dc _ZN7android6QmiCsd14setDhaSolutionERKNS_7String8E
00000000 DF *UND* 00000000 memset
00000000 DF *UND* 00000000 strlen
00000000 DF *UND* 00000000 memcpy
00000000 DF *UND* 00000000 strtok_r
00000000 DF *UND* 00000000 atoi
00000000 DF *UND* 00000000 ss_audio_SetDhaSolution
00000000 DF *UND* 00000000 __android_log_print
00000000 DF *UND* 00000000 __stack_chk_fail
00000000 DO *UND* 00000000 __stack_chk_guard
00001185 g DF .text 00000028 _ZN7android6QmiCsd13setStartVoiceEv
00000000 DF *UND* 00000000 csd_client_start_voice
000011ad g DF .text 000001a8 _ZN7android6QmiCsd11setLoopbackEiii
00000000 DF *UND* 00000000 csd_client_pcm_loopback_stop
00000000 DF *UND* 00000000 ss_audio_packet_loopback_stop
00000000 DF *UND* 00000000 csd_client_stop_voice
00000000 DF *UND* 00000000 csd_client_pcm_loopback_start
00000000 DF *UND* 00000000 ss_audio_packet_loopback_start
00000000 DF *UND* 00000000 csd_client_switch_device
00001355 g DF .text 00000028 _ZN7android6QmiCsd9setRxMuteEb
00000000 DF *UND* 00000000 csd_client_stream_mute
0000137d g DF .text 0000002c _ZN7android6QmiCsd8setWbamrEb
00000000 DF *UND* 00000000 ss_audio_set_network_id
000013a9 g DF .text 00000040 _ZN7android6QmiCsd14setVoiceVolumeEif
00000000 DF *UND* 00000000 csd_client_volume_index
00000000 DF *UND* 00000000 _ZdlPv
00001405 g DF .text 00000028 _ZN7android6QmiCsdD2Ev
00000000 DF *UND* 00000000 pthread_mutex_destroy
0000142d g DF .text 00000012 _ZN7android6QmiCsdD0Ev
00001405 g DF .text 00000028 _ZN7android6QmiCsdD1Ev
0000143f g DF .text 00000018 _ZN7android6QmiCsd10setDualMicEb
00001459 g DF .text 0000006c _ZN7android6QmiCsd12setTtyDeviceEiii
00000000 DF *UND* 00000000 csd_client_tty
000014c5 g DF .text 0000004c _ZN7android6QmiCsd9setTxMuteEb
00000000 DF *UND* 00000000 csd_client_mic_mute
00001511 g DF .text 00000198 _ZN7android6QmiCsd12setVoicePathEii
00000000 DF *UND* 00000000 pthread_mutex_lock
00000000 DF *UND* 00000000 pthread_mutex_unlock
000016a9 g DF .text 00000044 _ZN7android6QmiCsdC2Ev
00000000 DF *UND* 00000000 pthread_mutex_init
00002de8 g DO .data.rel.ro 00000064 _ZTVN7android6QmiCsdE
000016a9 g DF .text 00000044 _ZN7android6QmiCsdC1Ev
000016ec g DF .text 0000000c __on_dlclose
00000000 DF *UND* 00000000 __cxa_finalize
00003000 g D .bss 00000000 __dso_handle
00002e50 g D .init_array 00000000 __INIT_ARRAY__
00002e58 g D .fini_array 00000000 __FINI_ARRAY__
00003000 g D *ABS* 00000000 _edata
00003000 g D *ABS* 00000000 __bss_start
00003010 g D *ABS* 00000000 _endand libcsd-client.so: (google calls functions like csd_client_start_voice explicitly.
Code:
DYNAMIC SYMBOL TABLE:
00000000 DF *UND* 00000000 __android_log_print
00000000 DF *UND* 00000000 __aeabi_unwind_cpp_pr0
00000000 DF *UND* 00000000 pthread_mutex_lock
00000000 DF *UND* 00000000 pthread_cond_signal
00000000 DF *UND* 00000000 pthread_mutex_unlock
00000000 DF *UND* 00000000 memset
00000000 DF *UND* 00000000 strlcpy
00000000 DF *UND* 00000000 qmi_client_send_msg_sync
00000000 DF *UND* 00000000 __stack_chk_fail
00000000 DO *UND* 00000000 __stack_chk_guard
00004969 g DF .text 00000028 csd_get_service_object_internal_v01
00000000 DF *UND* 00000000 qmi_client_notifier_init
00000000 DF *UND* 00000000 qmi_client_get_service_list
00000000 DF *UND* 00000000 pthread_cond_wait
00000000 DF *UND* 00000000 qmi_client_release
00000000 DF *UND* 00000000 qmi_client_init
00000000 DF *UND* 00000000 qmi_client_register_error_cb
00000000 DF *UND* 00000000 clock_gettime
00000000 DF *UND* 00000000 pthread_cond_timedwait
00000000 DF *UND* 00000000 qmi_client_send_msg_async
00000000 DF *UND* 00000000 __aeabi_unwind_cpp_pr1
00003281 g DF .text 00000624 csd_client_start_voice
000038a5 g DF .text 00000128 csd_client_enable_device
000039cd g DF .text 000000c8 csd_client_disable_device
00003a95 g DF .text 000000b0 csd_client_start_record
00003b45 g DF .text 000000a4 csd_client_stop_record
00003be9 g DF .text 000000a8 csd_client_start_playback
00003c91 g DF .text 00000098 csd_client_stop_playback
00003d29 g DF .text 000000c8 csd_client_volume
00003df1 g DF .text 00000064 csd_client_mic_mute
00003e55 g DF .text 0000004c csd_client_wide_voice
00003ea1 g DF .text 0000006c csd_client_slow_talk
00003f0d g DF .text 0000006c csd_client_fens
00003f79 g DF .text 00000084 csd_client_volume_index
00003ffd g DF .text 000001b0 csd_client_switch_device
000041ad g DF .text 00000060 csd_client_stream_mute
0000420d g DF .text 00000208 csd_client_pcm_loopback_start
00004415 g DF .text 00000134 csd_client_pcm_loopback_stop
00004549 g DF .text 00000060 csd_client_tty
000045a9 g DF .text 00000078 csd_client_deinit_lb
00004621 g DF .text 00000094 csd_client_init_lb
000046b5 g DF .text 000002b4 csd_client_stop_voice
0000a010 g DO .bss 00000004 csd_condition
0000a014 g DO .bss 00000004 csd_cond_mutex
0000a07c g DO .bss 00000004 csd_state_mutex
00009630 g DO .data.rel.ro.local 00000030 csd_qmi_idl_service_object_v01
00000000 DO *UND* 00000000 common_qmi_idl_type_table_object_v01
00004990 g DF .text 0000000c __on_dlclose
00000000 DF *UND* 00000000 __cxa_finalize
0000a080 g D .bss 00000000 __dso_handle
00009e7c g D .init_array 00000000 __INIT_ARRAY__
00009e84 g D .fini_array 00000000 __FINI_ARRAY__
0000a008 g D *ABS* 00000000 _edata
0000a008 g D *ABS* 00000000 __bss_start
0000a090 g D *ABS* 00000000 _endI was thinking we could skip libaudio-ril.so all together and call functions in libcsd-client just like google does. Problem is, the audio libcsd functions are made for qualcomm based chipsets and Samsung does mash-up functions from their own exynos alsa implementation (for everything except ril) and some functiosn via libaudio-ril.so to interact with qualcomm's stuff. Unfortunately trying to guess what exactly is happening: which functions are being called, what is the function signature exactly (parameters, return values) and in what order are they called is nearly impossible. We can try abandoning the entire exynos audio implementation and pretend to be qualcomm. Basically that will give us the qualcomm libraries that google uses for the nexus 4 for example but I highly doubt that this will even work given the very different hardware so I didn't pursue that path.
How to fix this?
1. Get the sources for the library (audio.primary.smdk4x12) that we use from Samsung. After all, the other exynos GSM phones do have that library open sourced somehow although it is not applicable or complete for us. I'm not sure who to contact about that.
2. Some genius reverse engineers audio.primary to figure out what exactly is going on. This is time consuming and is way beyond my league.
3. Mix the exynos audio.primary with the qualcomm audio.primary to try and get things rolling. To me though, the odds of getting this working are very slim. You'll be shooting in the dark. Maybe someone is more capable of disecting the library and have some more educated guesses as to what is going on.
4. Wait until Samsung releases 4.2 for any exynos + qualcomm lte phone. We can then use the libraries without knowing what exactly happens behind the scenes just like what we currently have in CM10.
I understand the community's frustration at samsung's lack of documentation and source.
Two things I already tried as well just in case someone wants to try them: 1. Backport the HAL JB library. It eventually crashed due to API compatability. I overrode the explicit checks and that led to SIGFAULTs in mediaserver. 2. symlink and call functions in libaudio-ril.so instead of libsecril-client.so from our audio.primary.smdk4x12 sources. Didn't work. CSD library wasn't getting the correct voice path and I have no idea what API it uses or what it expects. I can elaborate more if someone is interested.
you're not able to boot at all with that sdcard? if the thing is stuck at the boot screen, you can logcat it and put it in pastebin so I can have a look. these issues are usually easy to solve once you got the logcat setup properly. (enable debugging in dev, install the sdk. use adb from terminal or cmd while the phone is connected via usb and bootlooping).
everything currently running in your phone is stored in ram
Last edited:
OK not going to quote that whole thing...I'll try and grab you a log and post it for you...thanks for that whole thing about ril audio very enlightening...as someone who is just learning about the deeper workings of android its an eye opener...as for our difficulties it really does seem to hinge on Samsung at this point esp seeing that the exynos expolit which can easily root a device or access all your RAM memory is connected to the camera...cuz that connection seems logical lol...and as for the what's in the RAM that's kind of what I feared lol...I'll get the log up later today thanks again for everything
Sent from my SGH-I317 using xda app-developers app
Sent from my SGH-I317 using xda app-developers app
Madmack - here is the link to my logcat I hope it helps. The steps I did;
reboot phone
start adb logcat
let it loop for a few minutes
pull sd card
finish boot
let the log settle
stop log
I hope its as verbose as possible and I hope this might help myself and anyone else with the sd card issue.
https://www.dropbox.com/s/bbemv1d7k6w7x00/MBLogcat_bootloop_sdcard_20121912.txt
reboot phone
start adb logcat
let it loop for a few minutes
pull sd card
finish boot
let the log settle
stop log
I hope its as verbose as possible and I hope this might help myself and anyone else with the sd card issue.
https://www.dropbox.com/s/bbemv1d7k6w7x00/MBLogcat_bootloop_sdcard_20121912.txt
This looks bad man. Did you copy and paste that into some windows notepad program before putting it up on dropbox? The new line characters are all gone so we end up with a big wall of text that is so hard to read.
For example, the very first line "( 1984): Welcome to Android 4.1.2" This should start a new line and continue from the existing one. I recommend pasting the goodies into notepad++ if you're using windows or simply just put up the log.txt file that you've piped to using "adb logcat > log.txt".
stand by ill fix it post haste
formating doesn't like me...working on it tho
there we go...here is new link and it is saved as an xml file to retain formatting
https://www.dropbox.com/s/bojr2aehdrqb73x/MBLogcat_bootloop_sdcard_20121912.xml
I even reinserted the sd card at the end of the log just to add more info for you
Last edited:
that looks like your problem:
Code:
E/JavaBinder( 4789): !!! FAILED BINDER TRANSACTION !!!I'm not sure how a userland app is able to bring down the entire zygote system but it really does look like an app or system partition issue.
Factory reset, wipe system. flash cm10 without any gapps data.. put in your sdcard and see if you can boot.
ill give it shot...gunna take me a little bit have to charge up lol
---------- Post added at 11:54 AM ---------- Previous post was at 11:46 AM ----------
yay
http://www.androidpolice.com/2012/1...national-galaxy-note-n7000-and-note-ii-n7100/
i hope they credit it you for some of this...here the link to the get.cm
http://get.cm/?device=n7100&type=nightly
D
Deleted member 2842059
Guest
These are GSM phones. Audio was never an issue for them
Credit me? No man, I actually used their work to get stuff working on this rom. lol. They did most of the heavy weightlifting: camera, audio, hwcomposer, sdcards, sensors.. I only put in gps and radio given that this is where we differ.
No CM (or AOSP) is out for any LTE Exynos phone so far afaik. So we're even further from being rolled as a nightly. I might be able to get our current CM10 into the nightlies but that's about it.
Of course if we can figure that audio routing issue. Getting the I317 (and all LTE variants) into CM (both 10 and 10.1) will be much easier.
These are GSM phones. Audio was never an issue for them
Credit me? No man, I actually used their work to get stuff working on this rom. lol. They did most of the heavy weightlifting: camera, audio, hwcomposer, sdcards, sensors.. I only put in gps and radio given that this is where we differ.
No CM (or AOSP) is out for any LTE Exynos phone so far afaik. So we're even further from being rolled as a nightly. I might be able to get our current CM10 into the nightlies but that's about it.
Of course if we can figure that audio routing issue. Getting the I317 (and all LTE variants) into CM (both 10 and 10.1) will be much easier.
blasted...i got all excited...i was thinking of the porting of 7100 to 7105 stuff you were doing earlier...but you're right its better to work with what we have and go from there...but when not if we get official support we'll be here and watch the audio issues are going to be tied to something rediculous like the accelorometer or something like that...esp if the RAM exploit is tied the the camera...thanks samsung
Last edited:
1 and 2) is basically where ALL of the opensource audio HALs on every other Samsung device came from. We received ZERO assistance from Samsung for any of this. Not even header files for anything. For 4412 devices (which all have Wolfson audio) - the original source came from another Wolfson-based device (Nexus 7 I think...) and was adapted to I9300 by codeworkx (likely with some RE and some trial and error), adding the ril interface stuff (which he might have received some inspiration from via crespo). For Yamahell (4210 devices) it was initially a major reverse engineering effort by paulk of the Replicant project.
3) This is what you probably need to do. Look at how the qcom audio HAL for pure Qualcomm devices talks to libcsd-client. Look at places where the I9300 HAL is doing similar things with libsecril-client - then swap things. You're probably going to have to change the mappings around a bit and there WILL be trial and error. I had to do a similar thing with the Yamahell HAL - the original Replicant implementation was designed to talk to their RIL. I looked at it, and looked at how codeworkx did things on I9300, and started moving things over. For example, Replicant's source did some remappings internally to one of their RIL libraries, while the I9300 HAL had to do the same remapping before passing things to libsecril-client, so I needed to implement those remappings in the HAL. You might need to do the exact opposite as libcsd-client might use Android's standard enums (like Replicant's did) and not Samsung's screwy ones.
4) Having to do this too often is why most of the prior exynos4 maintainers have declared their current devices to be the last ones they'll mess with.
IF no one has succeeded by mid-late January, I *MIGHT* be willing to accept a temporary loaner device for 2-3 weeks so I can take a crack at it. No guarantees of success and I am NOT accepting a permanent donation (only a loan), I don't want to be stuck with another Exynos device sucking my time for more than a short attempt. I would rather that someone else do it though, both for the sake of my free time and so others can gain more experience... Teach a man to fish and all that...
Last edited:
alright...did a factory rest, system wipe, dalvick and cache, nothing else but ROM flash...card is formated to FAT32...and I got nothing...boot loop until card is removed...finishing up a log for you sir
https://docs.google.com/open?id=0BzJOrW_SUj_-QkJ1MlFxYUVVLXc
in xml format should hopefully be able to download that
Last edited:
Have you considered there might be a problem with you sd-card? What EXACT model is it.
i have considered it but it mounts fine to a computer (with adapter) no problem i can delete the partition and make it whatever i want, transfer stuff to and from it no problem, but i get nothing when its in the phone...here is the link to the exact card on newegg
http://www.newegg.com/Product/Product.aspx?Item=N82E16820171582
only thing i can think of is the class is messing with something, but it worked just fine out of the package in the Stock TW based ROMs
found this not sure if it helps
Code:
E/kickstart-qcks( 1998): Spawning efsks
I/kickstart-efsks( 2984): EFS_TTY='/dev/ttyUSB0'
I/kickstart-efsks( 2984): Parsing 'where to save memorydump' options
I/kickstart-efsks( 2984): PathToSaveFiles='/dev/block/platform/dw_mmc/by-name/'
I/kickstart-efsks( 2984): EFSKS parameters
I/kickstart-efsks( 2984): EFS_TTY='/dev/ttyUSB0'
I/kickstart-efsks( 2984): ks_path='/system/bin/ks'
I/kickstart-efsks( 2984): PathToSaveFiles='/dev/block/platform/dw_mmc/by-name/'
I/kickstart-efsks( 2984): RX_Timeout=-1
E/kickstart-efsks( 2984): File '/dev/ttyUSB0' was not found
E/kickstart-efsks( 2984): /dev/ttyUSB0 does not exist.
E/installd( 2007): eof
E/installd( 2007): failed to read size
I/installd( 2007): closing connection
I/Zygote ( 2003): Exit zygote because system server (2444) has terminated
I/ServiceManager( 1996): service 'SecTVOutService' died
I/ServiceManager( 1996): service 'media.audio_flinger' died
I/ServiceManager( 1996): service 'media.player' died
I/ServiceManager( 1996): service 'media.camera' died
I/ServiceManager( 1996): service 'media.audio_policy' died
I/Netd ( 3113): Netd 1.0 starting
D/AndroidRuntime( 3112):
D/AndroidRuntime( 3112): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
Last edited:
no friggin' clue. can't see anything meaningful in the logs. thing won't boot without the sdcard inserted you say?
- Status
Similar threads
- Poll
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
51
here is a little status update coz I know how much you guys love em :
we're close to getting cm10.1 with stock audio hal (read: closed source samsung stuff) that I used in cm10 running.
This should pave the way for official support but with the stock hal kinks. Once we roll this out, we'll continue working on disecting the decompiled library to hopefully get open source audio rolling eventually.
In any case, I don't think we're far from seeing official cm10.1 support. No precise ETA. We'll also try to roll one ROM for three devices : at&t's, tmobile and the international variant.40As promised Here is the decompile of the file in c.
https://docs.google.com/open?id=0B0g-ojj_rL70OFlpTnBwRjE3N3c
I had it private should be ok now
Sent from my SGH-T889 using xda app-developers app36After finishing my work on porting CM10 to our beloved device, I started playing around some files and compiling to see if we can get our sweet i317 rolling android 4.2.
I present to you the file I currently have, flash using the following steps:
Make sure you're using TWRP 2.3.2 or higher. (Earlier versions don't support 4.2)
1. download the file.
2. download gapps (search google. Hint: gapps-jb-20121212).
3. put them both on your sdcard.
4. reboot into recovery.
5. wipe "system" and factory reset.
6. flash the downloaded file, then the 4.2 gapps that you downloaded and reboot.
What works:
-Audio in speaker, headphones.
-Camera?
-GPS?
-Radio works with LTE speeds.
What doesn't work:
-In call audio.
This rom is tested and should work on these similar devices:
1. AT&T Note 2
2. T-MOBILE Note 2
3. International LTE Note 2
IMPORTANT:
If you want to revert back to a jellybean 4.1.x rom. You'll find that all of your internal sdcard content is moved to a subfolder called 0. This is due to Android's new implementation of multi-user accounts. To get your files back to how they used to be, I created a little cwm file that you need to flash after restoring an old backup or flashing a 4.1 rom. Remember, you flash this file AFTER you restore or flash a 4.1 ROM. The file you need is attached.
Download
Dec 14: http://www.mediafire.com/?rzb9uipj801v1cp
31You're welcome.
Everyone don't forget the thanks button.
Sent from my SGH-T889 using xda app-developers app25
no original work? no one had anything remotely as close as this for any exynos lte device. we literally have everything working except in call audio which we're actively "originally working on".
my original work can be seen in my github commits.
Sorry bud, this doesn't belong in the development section. Please bring it back where it belongs.
New posts
-
-
Development [OFFICIAL] LineageOS 21 for the Google Pixel Tablet- Latest: hexaheximal
-