[ROM] 【4.2.2】【UNOFFICIAL】CyanogenMod 10.1.3.1【ON-HOLD】【GPL】 - HTC Rezound

[ROM] 【4.2.2】【UNOFFICIAL】CyanogenMod 10.1.3.1【ON-HOLD】【GPL】
MWF Nightlies
Freshly built every MWF Night​
{
"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"
}
CyanogenMod 10.1.3.1 is a free, community built distribution of Android 4.2.2 (Jelly Bean) which greatly extends the capabilities of your phone.​Features:
CM10.1.3.1
Koush's SuperUser is default
Android JB 4.2.2
Working OTA system - Requires CWM 6.x.x.x/TWRP 2.6.0.0 or later. Amon RA will not work.
Apollo
HDR Camera
CM's new "File Manager"
Lockscreen widgets - kinda
Scroll typed text with vol -/+ (CM settings)
Bluetooth Calling (Has been reported working, your results may vary)
Multi Language Support
Zipaligned
All images optimized
Installation InstructionsI recommend users of this rom to be on the latest firmware and Hboot with an s-off device. If you are not on the latest global firmware, here is how to do it.
NOTE: For recovery I use TWRP 2.5.0.0. Some wipe options below may not be included in other recovery options. Still wipe what is available the best you can.
1. Put the Rom on the root of your SD Card
2. Compare MD5 Sum
Windows: MD5 Calculator
LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
Mac: Open a terminal and type: md5 [path to the rom on your sd card]
3. Reboot to Recovery
4. Scroll down and select "Wipe"
5. Wipe the following:
Wipe ALL data/factory reset x2
Wipe /data x2
Wipe /cache x2
Wipe Dalvik-cache x3
Wipe /boot x2
Wipe /system x3
Optionally wipe:
Wipe battery stats
Wipe rotate settings​6. Scroll to and press return
7. Install Rom from SD Card
8. Reboot and enjoy!​Further questions about the ROM
Please check the FAQ in the second post.​
Note: Please do not mirror the Rom. Thanks.​NOTICE: I do not provide a changelog. However, you may view the official CM changelog by clicking CHANGELOG​​
Downloads:
ROM: DOWNLOAD
----------------------------------------------------------------------------------------
GApps: gapps-jb-20130812-signed.zip​
signatures.mobile-overload.com
​ I wanted to say thanks to Chad and everyone else involved in getting AOSP based ROMs working on the Rezound. Without our talented group of devs, none of this would be possible.​Source:
Google - Android
Cyanogen - Source
Chad0989 - Made it possible to run AOSP based roms on the Rezound
Vigor - Beta builds
Vigor - Kernel
Please see post two for additional notes.​

Frequently Asked Questions
HTC Rezound UNOFFICIAL CM10.1.3 (JB-4.2.2)​
This is a short list of Q&A that should help you find answers to the questions you might have concerning flashing and using this ROM.​
[SIZE=+1]Q1: What version of Android is this?[/SIZE]
This Rom is CM10.1 which is currently built on Android 4.2.2.​
[SIZE=+1]Q2: I looked but did not see a changelog in the op. How can I track your changes?[/SIZE]
I do not provide a changelog but you can track CM's official changelog for recent changes.
You can also find device specific changes by looking at Flyhalf205's Github​
[SIZE=+1]Q3: Is this ROM S-On compatible?[/SIZE]
By default, no. Follow these instructions to flash on an S-On device:
NOTE:
You must have the Android SDK downloaded and installed onto your computer.
You must be familiar with the SDK's install directory structure.
You must be familiar with using terminal and know how to cd to the platform-tools folder of the Android SDK's install directory.
1. Open the Rom zip with an archive tool such as 7zip and extract the boot.img from it.
2. Place the boot.img into the platform-tools folder of the Android SDK's install directory.
3. Put the Rom and GAPPS on the root of your SD Card
4. Compare MD5 Sum
Windows: MD5 Calculator
LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
Mac: Open a terminal and type: md5 [path to the rom on your sd card]
5. Reboot to Recovery
6. Scroll down and select "Wipe"
7. Wipe the following:
Wipe ALL data/factory reset x2
Wipe /data x2
Wipe /cache x2
Wipe Dalvik-cache x3
Wipe /boot x2
Wipe /system x3
Optionally wipe:
Wipe battery stats
Wipe rotate settings
Click to expand...
Click to collapse
8. Scroll to and press return
9. Install Rom and gapps (in that order) from SD Card
10. FOR GSM USERS ONLY - After flashing the ROM and GAPPS, re-wipe /data and then flash the GSM patch
11. Return to the main menu of the recovery and select "Developer Menu".
12. Select "Reboot to bootloader
13. Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
14. Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
15. Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
16. Watch the output of the terminal, it should say something like "sent successfully".
17. Finally send this command:
Code:
fastboot reboot
This command reboots your device into Android. Wait for it to boot up and enjoy your new freshly installed CM10.1.
Note: If you are having issues connecting your device to your windows computer in fastboot, please insure the drivers are up to date by installing the latest version of HTC Sync for the Rezound.​
[SIZE=+1]Q4: Where did the Developer options in settings go?[/SIZE]
Google/Android has hidden this feature in JB 4.2.1 and up. Follow these steps to re-enable the feature:
Go to settings > about phone. Tap Build Number 7 times. Tapping Build Number 7 times re-enables the Developer Options in settings.​
[SIZE=+1]Q5: Where did the reboot menu go?[/SIZE]
In Android 4.2.2 this menu is hidden by default in CM10.1 and must be enabled.
Step 1: Enable Developer options using the method described in Q4.
Step 2: Go to Developer options and check the Advanced reboot box.
Step 3: Go to System settings > System > power menu. Insure the Reboot menu box is checked.
Click to expand...
Click to collapse
[SIZE=+1]Q6: What is the recommended HBOOT and Radio for this ROM?[/SIZE]
RADIO: 2.23.10.0123r, 2.23.10.0124r
HBOOT: 2.28
Click to expand...
Click to collapse
If your device is not using this firmware and HBOOT, its very simple to update. Just follow the guide HERE to get updated.​
[SIZE=+1]Q7: Is this ROM GSM compatible?[/SIZE]
Yes. You must enter Mobile Networks and change preferred network list to GSM.​
[SIZE=+1]Q8: Can you add in [insert name] mod?[/SIZE]
No. By default this ROM will remain bone stock without any modification. It is intended to be the purest form of CM on this forum for the Rezound. However, user created mod submissions are welcome and will be added to the third post (Mods section) if they fit the standards outlined for this ROM.​
[SIZE=+1]Q9: When will such and such bug be fixed?[/SIZE]
Bug fixes are always being worked on. As the fixes are made available, they will be included in the next update version of this ROM.​
[SIZE=+1]Q10: This ROM seems a little choppy. Is there anything I can do?[/SIZE]
Go into Developer options and disable hardware overlays.
NOTE: You must disable hardware overlays every time you reboot.​
[SIZE=+1]Q11: I notice that Superuser isn't in the app drawer, where did it go?[/SIZE]
Recently CyanogenMod has merged in Koush's new Superuser configuration. Starting in build 20130310 you will now found all Superuser settings in the System settings under the Superuser tab.​
[SIZE=+1]Q12: How do I zoom in the camera?[/SIZE]
In the camera app place two fingers on the screen and spread rapidly ​
[SIZE=+1]Q13: How can I optimize my battery life on this ROM?[/SIZE]
XDA member md303 has written a very helpful post describing their battery usage and what they have done to optimize it for better life. Check it out HERE​
[SIZE=+1]Q14: Why isn't my WiFi working?[/SIZE]
You're most likely s-on then. You must flash the boot.img that comes with the .zip inside of fastboot.​
If your question is not answered here or you need further help, go to the official Support Thread for this ROM. DO NOT post questions directly in this thread.​

MODS UNOFFICIAL CM10.1
Provided by the community​
NOTE: User created mod submissions must follow the standards of this ROM for acceptance.
All mods must:
Blend into the ROM as if they were originally entended to be there stock
Must not break any of the other features of the ROM
Must not be designed to leverage harm unto the devices of the other users of this ROM
Should be intended to improve features of the ROM rather than replace those features
If the mod is entended to be used as a theme, it must present a professional and clean appearance
Must not violate the licenses that cover CM. Open source mods only.
Must be flashable in recovery
If your mods and themes are not to these standards, they will not be accepted!
Onto the Mods​
Want to set the dpi for apps individually like you can with Paranoid Settings in Paranoid Android?
Get the Xposed Framework to do so HERE
Click to expand...
Click to collapse
Safety! Control what info of yours your apps can detect.
update-cm-vigor-20130320-openpdroid.zip created by manchucka
Click to expand...
Click to collapse
Prefer SuperSU to Superuser?
SuperSU created by manchucka
Click to expand...
Click to collapse
No-Split MMS
Find it here created by socialruins
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Re: [ROM][JB][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Awesome sauce, thanks for being the human build machine and getting this out to us, and of course thanks to the devs responsible for getting this to work on our rezounds!
Edit: won't download on mobile oh well to the computer I go! (what is this? 2008?)
Sent from my ADR6425LVW using xda app-developers app

Squirrel1620 said:
Awesome sauce, thanks for being the human build machine and getting this out to us, and of course thanks to the devs responsible for getting this to work on our rezounds!
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
No problem. Happy to do it with Chads blessings

Wow... so much development lately! Thanks a lot for all your hard work!
:good:

is this 4.2?

ryclegman said:
is this 4.2?
Click to expand...
Click to collapse
Yes, 4.2.1

If your having trouble downloading from mobile, please take note what server on @androidfilehost you are attempting to download from. I will need this info so I can file a report. Thanks

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Oh my! Welcome back
Sent from my Rezound using Tapatalk 2

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
wildstang83 said:
If your having trouble downloading from mobile, please take note what server on @androidfilehost you are attempting to download from. I will need this info so I can file a report. Thanks
Click to expand...
Click to collapse
(CA) server #5
Sent from my ADR6425LVW using xda app-developers app

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Restore contacts from sim card shows there are no contacts. Should be 12ish. Playing without gapps for a bit.
Sent from my ADR6425LVW using Tapatalk 2

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Hey, I don't know if anything has changed but last I recall Chad doesn't want to hear any bug reports at all. That was one of the rules when we were told we could post builds, so you might wanna edit the OP so people don't bug him about it. Unless he has specified otherwise, then by all means, feel free.
Sent from my SCH-I535 using xda premium

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Yup my bad. Totally forgot about that.

Loving it so far. Only thing I noticed is that the camera doesn't zoom. Thanks for sharing this stang!
Nevermind you zoom with the volume buttons instead of pinch to zoom

No wifi tether on this. I'll skip it til I can look further into it.

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
Pmem or ION?
Sent from my ADR6425LVW using Tapatalk 2

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
GoldenCyn said:
Pmem or ION?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
pmem
Sent from my Rezound using xda premium

Re: [ROM][JB-4.2.1][CDMA] CM10.1 KANG for HTC Rezound [1-21-13]
live2die said:
pmem
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
Yup just tested with my basic kernel and it works. So I assume this is pmem not ion. I'm not near a WiFi device can someone see if tether works using my kernel? It always has worked with mine on cm10
Sent from my ADR6425LVW using xda app-developers app

highdro said:
Loving it so far. Only thing I noticed is that the camera doesn't zoom. Thanks for sharing this stang!
Nevermind you zoom with the volume buttons instead of pinch to zoom
Click to expand...
Click to collapse
I have no idea if this is a kernel thing but I'm running a different persons build and shrikes kernel and it zooms

Related

Cannibal Open Touch v2.1 (latest update: 12/1/2012)

{
"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"
}
Project Open Cannibal presents...
Cannibal Open Touch v2.1 for Asus Nexus 7​
About Cannibal Open Touch:
Cannibal Open Touch is the next generation of custom recoveries. Jam-packed with cool and useful features, it can handle just about anything you can throw at it.
Main Features:
1. Theme support
2. Touch screen button controls!
3. GooManager support!
4. Advanced Backup
5. Delete old backups!
6. Persistent settings
7. User-defined backup locations!
8. ADB Sideload
9. Touchscreen calibration
Why the name Cannibal Open Touch?
Because we can. The name also embodies everything that Cannibal Open Touch is. It is no longer just a variant of ClockworkMod Recovery, it is it's own recovery by itself. Combining features from ClockworkMod 5, Team UtterChaos' Sony Xperia recovery, AmonRa 3.0.6, Xionia CWMA and a heaping helping of our own special enhancements it is truly revolutionary.
What to do when an error occurs:
DO NOT simply say "xxxx doesn't work" as that is highly unhelpful and will probably be ignored. Instead, post the recovery log! To grab a log when an error occurs, simply open a terminal (or command prompt if on Windows), "cd" to an easily accessible directory and execute:
Code:
adb pull /tmp/recovery.log
Paste the log as an attachment (don't paste the text inside, as it can be quite lengthy), or paste it on pastebin.com.
WARNING!
If you are upgrading from a previous version of Cannibal Open Touch you must delete the settings.ini file located in the cotrecovery folder on your sdcard!
The Cannibal Open Touch App for Android (separate from this recovery image, which is fully functional on all devices) is *NOT* functional on Nexus 7 devices running Android 4.2 or later. A fix is being investigated.
Flashing instructions:
1. Download the Cannibal Open Touch recovery image.
2. Reboot your device to bootloader mode (adb reboot bootloader)
3. Flash the image with fastboot (fastboot flash recovery /path/to/recovery.img)
4. Reboot to recovery mode
5. PROFIT!
Main Recovery Screenshots
Main Gallery (external link)
Available Themes:
Themes Gallery (external link)
Download Cannibal Open Touch v2.1:
Note: The below link is an external link to the Project Open Cannibal forums. We do not require registration to download any public release, but we'd sure appreciate it if you stopped by to say hello
WARNING!
This has only been tested on the non-3g models (grouper/nakasi); while it is hightly probable this will work on the nakasig we cannot confirm this at this time (at best I would expect assert errors with rom zips).
Cannibal Open Touch Download
XDA:DevDB Information
Cannibal Open Touch, a Tool/Utility for the Nexus 7
Contributors
Sblood86, drewwalton19216801, thenameisnigel
Version Information
Status: Stable
Current Stable Version: 2.1
Stable Release Date: 2012-12-01
Created 2013-09-05
Last Updated 2013-09-05
Thanks this looks awesome, I will definantly use it when it supports 4.2. I may give it a shot on 4.1.2 though to see what it is all about
mlaws90 said:
Thanks this looks awesome, I will definantly use it when it supports 4.2. I may give it a shot on 4.1.2 though to see what it is all about
Click to expand...
Click to collapse
Yeah Drew (the other dev on the project) wrote in that warning there; it's referring to the Android control application that he did. Allows you to easily change the persistent settings from within android instead of recovery (including but not limited to the user defined backup paths). The recovery does work in 4.2, the app does not.
To set user defined backups you could use the app in 4.1 or older than upgrade the settings will remain in place; or manually create a file in sdcard/cotrecovery/ with the title .userdefinedbackups and the sdcard folder you would like backups saved to: for example if you wanted to add rom manager compatibility you would want your backups to be in '/sdcard/clockworkmod/' so in the .file you would simply write 'clockworkmod' without the quotes.
Sblood86 said:
Yeah Drew (the other dev on the project) wrote in that warning there; it's referring to the Android control application that he did. Allows you to easily change the persistent settings from within android instead of recovery (including but not limited to the user defined backup paths). The recovery does work in 4.2, the app does not.
To set user defined backups you could use the app in 4.1 or older than upgrade the settings will remain in place; or manually create a file in sdcard/cotrecovery/ with the title .userdefinedbackups and the sdcard folder you would like backups saved to: for example if you wanted to add rom manager compatibility you would want your backups to be in '/sdcard/clockworkmod/' so in the .file you would simply write 'clockworkmod' without the quotes.
Click to expand...
Click to collapse
Oh see, that is not a big deal at all. I would be willing to give that a shot, didn't even know there was an app Thanks for the detailed reply, I'm sure it will help others as well.
The recovery looks nice ^_^
Don't know why I prefer unique recoveries and not popular ones
I like the look of this recovery, I have nothing as of yet to flash, but I'll definitely be keeping it
Thanks
Sent from my SGH-I747 using xda premium
OK just to clarify, this does work 100% with 4.2.1 ROMs? And where can i find some themes for it.....looks verrrrrrry promising
Edit...and I'm not concerned about backups as i never use them.... FULL wipe every time for me
Sent from my Nexus 7 using xda premium
lightninbug said:
OK just to clarify, this does work 100% with 4.2.1 ROMs? And where can i find some themes for it.....looks verrrrrrry promising
Edit...and I'm not concerned about backups as i never use them.... FULL wipe every time for me
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yes the recovery works w/ 4.2 roms the only issue is the app that Drew did not being able to communicate with the sdcard properly in 4.2 (this is not related to the recovery itself).
Themes we could use more of; there is an outline of them on our forums and on github (nexus 7 is of course the jb-800x1200 branch)
Looks nice gonna give it a run through
Are there any sources? I kind of want to build this for my spectrum or do you not have plans for open source
Sent from my Nexus 7 using Tapatalk HD
azoller1 said:
Are there any sources? I kind of want to build this for my spectrum or do you not have plans for open source
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I apologize; I ripped the thread layout off from Drew and didn't realize the source was not linked. I'll get it linked in the OP at a later time but for now suffice it to say yes we have open sourced everything; we have full intention of open sourcing all future related code as well (hence the 'Open' part of the name ):
Either sync a CM10 tree or use the jellybean branch in Drew's hacked up manifest (this will only build recovery).
Whichever way you sync your repo you will need to replace the recovery folder (Drew's manifest is pulling the old repo)
you will need the jellybean branch from the recovery itself:
android_bootable_recovery
if you used Drew's manifest you should already have the following if not you will want to pull these as well:
the jellybean branch from here
android_bootable_recovery_gui
and the master from here
android_bootable_recovery_res
Lastly; a slightly modified grouper device repo (pretty sure this one is also for recovery only lol)
I'll definitely give this a run when I can later today!
Pretty Awesome. Installed just fine on my Nexus7 WiFi. Gonna run this for a while and see how she goes, tnx!
Quick question, is there a way to flash this without a computer? As u currently don't have one and could I use my twrp backup if anything are to happen or would I need to make a new one with this recovery?
Sent from my Nexus 7 using Tapatalk HD
xfrancis14 said:
Quick question, is there a way to flash this without a computer? As u currently don't have one and could I use my twrp backup if anything are to happen or would I need to make a new one with this recovery?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
You need to use fastboot, which requires use of a computer (for now). TWRP backups are not compatible so yes you would need to make a new backup.
Okay well I don't currently have a computer so I guess ill stick with twrp for now and okay
Sent from my Nexus 7 using Tapatalk HD
Is it possible for you to make an app which would flash the recovery? If so that would he amazing as I really want to try this recovery
Sent from my Nexus 7 using Tapatalk HD
xfrancis14 said:
Is it possible for you to make an app which would flash the recovery? If so that would he amazing as I really want to try this recovery
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Well... If the nexus 7 supports flash_image or dd (which I have no idea if it does, you'll have to find out or ask Drew) than yes it's possible; than again you could simply do it from a terminal emulator in that case. Fastboot is the safest way in particularly without having the device myself to play with.
finally got a chance to test her out, so far so good!
not the absolute best advance since sliced bread but i do love seeing an alternative!
as of now i give it a 7 out of ten being no problems i can find, everything seems to work but dont feel as if im gaining much over my other recovery options... that said i felt the same way at first with 4ext recovery and now i absolutely love it, so ill let you know if this moves to 10 out of 10 an time soon
thanks again for giving me options!

[ROM][4.2.2 JDQ39 AOSP] Eos 4.0 -- Grouper

{
"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"
}
Welcome to Eos 4.0! The Eos project originated with the AOSP release of ICS, and was originally founded by Solarnz and co founded by Bigrushdog. Since then, Eos has evolved into a multinational collaborative effort backed by top Android developers. Our objective is to provide a world class AOSP build with unique features and enhancements. Eos is an ongoing development project in which builds are released on a regular basis. Every release should be considered stable and highly functional.
Solarnz - Project founder and backend systems admin
Bigrushdog - Project lead, Chief Developer
Kevdliu - Feature Engineer, Toro maintainer
Timduru - Frameworks Developer, TF101 maintainer
Roach - Frameworks Developer - N4 maintainer
RaymanFX - Remote branch and Experia maintainer
Runandhide05 - Xoom maintainer
UBER - Chief Graphics Designer
Sykomaniac - Maguro maintainer
Code:
NX Gesture Navigation Bar
Custom Quick Toggles Tiles with Brightness & Volume Seekbars
Softkeys Long-Press Actions
Custom Navigation Bar Ring Quick Launch Targets
EOS Status Bar Toggles
Navigation Bar Color w/ Project Glass (Auto-Transparency, not the Google Project Glass :P)
Status Bar Color
Battery Indicator Mods
Clock Mods
T-Mobile Theme Engine
Hide System Bars
Performance Settings
Volume keys switch depending on rotation. So the volume up key is always either on the top or to the right of volume down. (Toggle-able)
Default Volume Control Stream (Ring or Media)
Advanced power menu with reboot options.
Eos Control Center
MORE...
We give love and much respect to Cyanogenmod. The AOSP scene would not exist as it does today without them. We implement some of their branches to support legacy devices and features that users have demanded. The resources we use include, but are not limited to:
Features:
Code:
Phone: for T9 dialer support
MMS
T-Mobile Theme Engine
Branches:
Code:
libhardware, libhardware_legacy, system/core, system/netd, /system/vold, frameworks/native, frameworks/av, isolated frameworks/base cherry-picks,
and various qualcomm support related branches. We also use some qualcomm related branches from CodeAurora Forum.
Team EOS Grouper Nightly builds
Download
G-Apps Package
Because this is an AOSP based rom Google Apps are not included. To install Google Apps please flash the following package after installing the rom:
Gapps package
Nexus 7 comes with the stock aosp kernel.
These builds are designed to be installed from your favorite recovery. MAKE SURE YOU HAVE THE LATEST 4.2.2 COMPATIBLE RECOVERY.
Changlog
Contribute
Gerrit Review
Gitweb for GPL compliance
Ohai! Guess I'll jump in here.
Yup... Spoiled by the participating...
Caution - SDcard directory changes with 4.2 installation
For those of you that are new to 4.2 releases, be aware that installing and running this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash and start this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. I haven't tried the latest version of CWM, but it was a problem on the six week old version I had installed.
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Edit: Installed the latest version (as of 12/17) of CWM and it.too was unable to find my nandroid backup once it was moved to the /sdcard/0 directory by the 4.2 installation process. To restore my old rom I had to do a clean install, then install ES file Explorer, move the clockworkmod directory to /sdcard/ and THEN restore.
freecity said:
For those of you that are new to 4.2 releases, be aware that installing this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. I haven't tried the latest version of CWM, but it was a problem on the six week old version I had installed.
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Click to expand...
Click to collapse
You need to upgrade your recovery to the latest cwm or twrp. The issue has been fixed since 11/16
freecity said:
For those of you that are new to 4.2 releases, be aware that installing this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. (I haven't tried the latest version of CWM.)
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Click to expand...
Click to collapse
Its not "this ROM" its all 4.2 ROMs that do it. And the way to prevent the /0/0/0/0 is by updating your recovery to the latest CWM or TWRP.
the new multi user in 4.2.x moves all your internal data to /data/media/0 for the main device owner. And if you create another user you will see /1 for the second user and so on for however many users you add.
So on 4.2.x ROMs you will have one /0 and it needs to be like that, if you move all your data to /data/media you will have issues. The /0 is a must and is the way of the future.
Having said that I will say it again. If you haven't already you really need to update your recovery.
Also on the note of gapps you must use the gapps specifically for 4.2 not 4.1.1 if you don't use 4.2 gapps you will have gapps fc like crazy
The slider in the Quicksettings menu for brightness is very laggy. Volume seems fine though. Also, my battery meter in Quicksettings sometimes says 0%, even though I'm at 97%.
runandhide05 said:
Its not "this ROM" its all 4.2 ROMs that do it. And the way to prevent the /0/0/0/0 is by updating your recovery to the latest CWM or TWRP.
the new multi user in 4.2.x moves all your internal data to /data/media/0 for the main device owner. And if you create another user you will see /1 for the second user and so on for however many users you add.
So on 4.2.x ROMs you will have one /0 and it needs to be like that, if you move all your data to /data/media you will have issues. The /0 is a must and is the way of the future.
Having said that I will say it again. If you haven't already you really need to update your recovery.
Also on the note of gapps you must use the gapps specifically for 4.2 not 4.1.1 if you don't use 4.2 gapps you will have gapps fc like crazy
Click to expand...
Click to collapse
The version of gapps I installed was 4.2 downloaded from the OP. I also tried a 4.2 gapps downloaded from another link so I was probably just missing a step somewhere or had a bad rom download, I'll try again tomorrow.
I do not believe I suggested that there was anything wrong with this or any other 4.2 rom (and certainly did not mean to suggest anything of the sort), only that there are important changes to be aware of when moving from 4.1 to 4.2 and back.
Thanks, will give it a try.
freecity said:
The version of gapps I installed was 4.2 downloaded from the OP. I also tried a 4.2 gapps downloaded from another link so I was probably just missing a step somewhere or had a bad rom download, I'll try again tomorrow.
I do not believe I suggested that there was anything wrong with this or any other 4.2 rom (and certainly did not mean to suggest anything of the sort), only that there are important changes to be aware of when moving from 4.1 to 4.2 and back.
Click to expand...
Click to collapse
Also note a full wipe is a MUST coming from any other ROM or even eos3
And I didn't read it as implying anything.
Just be sure to update recovery
All good Buddy
Does this have tablet ui? Can't use my nexus 7 without it. Lol
Sent from my Nexus 7 using xda premium
TheUndertaker21 said:
Does this have tablet ui? Can't use my nexus 7 without it. Lol
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
In a way.. It has the option to put the soft keys in the left side like tab ui but keeps the top status bar
Sent from my Nexus 7 using Tapatalk 2
Haha that'd do. Thanks for reply.
Sent from my Nexus 7 using xda premium
That's pretty sweet.
New build out. Eos is on a roll
Can we just dirty flash 45 over 44? Will gapps need to be reflashed again also?
44 was running pretty well. Already downloaded 45. Waiting on answer before I flash new build.
demandarin said:
Can we just dirty flash 45 over 44? Will gapps need to be reflashed again also?
44 was running pretty well. Already downloaded 45. Waiting on answer before I flash new build.
Click to expand...
Click to collapse
Dirty flash is fine.. I've had no issues going from 44 to 45
Sent from my Nexus 7 using Tapatalk 2
DJLamontagneIII said:
Dirty flash is fine.. I've had no issues going from 44 to 45
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yep..dirty flashed rom an reflashed gapps. All running well so far.
Unless instructed otherwise from eos4 nightly to nightly a dirty flash is fine.
Also the latest update fixes ALOT of the third party apps FC'ing.
So put firefox, kindle, and many more on the problem squashed list.
Anybody having issues using the latest nightlys with custom kernels? I tried using Franco's kernel and I am unable to install paid apps with it. I get the USB storage error.

[CM7][3.6][EU/US][Discontinued]CyanogenMod 7.2 - Samsung Galaxy Player 3.6

I recommend using CyanogenMod 10 (Android 4.1.2) on Samsung YP-GS1! =>http://forum.xda-developers.com/gal...-6-samsung-s-wifi-3-6-cyanogenmod-10-t3046129
CyanogenMod 7.2 for the Samsung Galaxy Player 3.6 EU/US
{
"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"
}
06/16/2020: All links have been restored and are working again. The files are the same. (Androthan)
Finally, here it is... CyanogenMod for our Galaxy Players 3.6!
Read before flashing!
FAQs
CyanogenMod FAQs: http://wiki.cyanogenmod.org/w/About
Samsung Galaxy Player FAQs: http://forum.xda-developers.com/showthread.php?t=2175920
Samsung Galaxy Player 3.6 FAQs: http://forum.xda-developers.com/showthread.php?t=2389347
Q: Can this completly destroy my device?
A: No, you will always able to restore your player via ODIN.
Q: Will this modify my bootloader?
A: No, it won't change anything on your bootloader.
Q: I want some more informations about this ROM, where can I get them?
A: Just send me an email/PM ([email protected]) or PM me.
Q: Can this used on a Galaxy Player 4.2?
A: CM7 for the 4.2: http://forum.xda-developers.com/showthread.php?t=2582138
Q: Do you allow me to modify and republish this ROM?
A: Of course!
Q: What's the difference between the US and the EU edition?
A: The US edition has got a touch sensitive home button and a different keyboard while the EU one
has got a physical home button.
Working - Not working
Working
- Button/screen backlight
- WiFi
- Vibrations
- Rotation
- GPS
- Compass
- CPU frequency control
- Shake detection
- Magnetic sensor
- Orientation sensor
- External storage (mounted on /sdcard)
- Internal storage (mounted on /sdcard/emmc)
- Audio
- Samsung SoundAlive
- ClockWorkMod recovery
- Low power mode
- Bluetooth
- Bluetooth music/sound streaming
- Video playback (For full screen mode -> Turn device right)
Working with bugs:
- Airplane mode (because of missing cell module)
Not working:
- Camera
- Microphone
Note: The phone feature is enabled (I can't disable it) but it won't use the battery or the CPU, it's just there but not usable. If you see 'Cell standby' in the battery stats, it means 'WiFi'
Changelog
Public preview - 13.12.2013
- First release
Beta 1 - 14.12.2013
- Fixed some bugs
- Fixed a bug with some wifi connections
- Added dhcpd server for TI SoftAP
Beta 2 - 19.12.2013
- Fixed Audio libs
- Fixed internal sd-card mounting
- Stability bugfixes
Beta 3 - 20.12.2013
- Fixed bluetooth: moved bluetooth chip firmware from /system/vendor/firmware to /lib/firmware
- Low power mode: Player doesn't boot the complete firmware, it just boots up in a "Low power mode" if a USB charger is detected
- Fixed CPU settings (thanks for mentioning it, @Quentinga)
- CWM recovery
Beta 4 - 10.01.2014
Fixed video playback
WiFi bugfixes
Stability bugfixes
Downloads
All hyperlinks are redirecting your download requests to my personal server. I'm using bitly as an intermediate for statistical purposes, so I can estimate how high the demand for the availability of this firmware still is. I'm not storing any personal data, if you're downloading the firmware via my server.
CyanogenMod 7.2 for Samsung YP-GS1 EU/US Beta 4: Download here
Google Apps (GMail, Play Store, Hangouts,...): Download here
Setup recovery for EU(You MUST use this one!): Download here
Setup recovery for US(You MUST use this one!): Download here
ODIN3 1.85: http://www.mediafire.com/download/82latn22s1kl7w2/andromint-Odin3-v1.85.zip
Kernels for US devices (capacitive home button)
US kernel for Beta 4: Download here
Installation guide
Note: You can also use CM without Google Apps!
Coming from Stock Samsung ROM
This will delete all data on your device!
Prepare PC
1. Download Google Apps, the Install recovery (tar-file) and ODIN3 and place them anywhere on your PC
2. Now, download the latest version for your device (EU or US); if you have an US device, also download the latest US kernel
3. Make sure you installed Samsung Kies (http://www.samsung.com/us/kies/) and the device drivers
4. Open ODIN3 and select the setup recovery, you downloaded in step 1, in the PDA section
3. Make sure nothing is checked except "F.Reset Time" and "Auto Reboot"
Prepare device
1. Make a backup of your data! (Not NANDroid)
2. Power off device
3. Boot to download mode
Prepare installation
1. Connect player with PC and wait until Odin detects your player
2. Select "Start" in Odin and wait until your device reboots
3. Power off your player
4. Boot to recovery mode
Install CyanogenMod (in recovery mode)
1. Make a NANDroid backup -> Select Backup/Restore -> Backup
2. Select -> Mounts/Storage -> mount USB mass storage
3. Connect device to PC
4. Copy the ROM and the Google Apps to your device
5. Unmount device from PC
6. Select: Factory reset -> Yes
7. Select: Install zip-file -> Choose zip from sd-card
8. Select the CyanogenMod zip and hit Yes (This will take up to 40 seconds)
9. Reselect: Choose zip file from sd-card
10. Select the Google Apps zip and hit Yes
11. Return to main menu -> Reboot (IF you have an US edition, hit "Power Off")
For US devices only
1. Reboot to download mode
2. Open ODIN3 and select the US kernel, you downloaded from this topic, in the PDA section
3. Flash
and reboot!
Upgrading/Switching from another CM7 build
Upgrading from V1.3 or higher
1. Download the newest version for your device (EU/US) and the Google Apps to your PC
2. Reboot your device to recovery mode (Long press power button -> Select Reboot -> Select Recovery)
3. In recovery mode: Select Mounts/Storage -> Mount USB storage
4. Connect device to your PC and copy the CyanogenMod zip-file and the Google Apps zip-file to your device
5. Unmount your device from your PC
6. Select Wipe cache -> Yes
7. Select Install zip-file -> choose zip from sdcard and select the CyanogenMod zip and hit Yes
8. Redo step 7, but with selecting the Google App package
9. Return to main menu and Reboot (IF you have an US edition, hit "Power Off")
For US devices only
1. Reboot to download mode
2. Open ODIN3 and select the US kernel, you downloaded from this topic, in the PDA section
3. Flash
and reboot!
Upgrading from V1.2 or lower
Prepare PC
1. Download the newest ROM for your device (EU/US) and the newest Install recovery (tar-file)
2. Open Odin
3. Select the Install recovery (Avaible in download section) in the PDA section
4. Make sure nothing is checked except "F.Reset Time" and "Auto Reboot"
Prepare device
1. Power off
2. Reboot to download mode
Prepare installation
1. Connect player with PC and wait until Odin detects your player
2. Select "Start" in Odin and wait until your device reboots
3. Power off your player
4. Boot to recovery mode
Installation
1. Select: Mounts/Storage -> Mount USB mass storage
2. Connect device to PC
3. Copy the ROM and the Google Apps to your device
4. Unmount device from PC
5. Select: Wipe cache -> Yes
6. Select the CyanogenMod zip and hit Yes (This will take up to 40 seconds)
7. Reselect: Choose zip file from sd-card
8. Select the Google Apps zip and hit Yes
9. Return to main menu -> Reboot (IF you have an US edition, hit "Power Off")
For US devices only
1. Reboot to download mode
2. Open ODIN3 and select the US kernel, you downloaded from this topic, in the PDA section
3. Flash
and reboot!
!ENJOY CM7!
The boot proccess after a first install or a upgrade can take up to 2 minutes!
Bugreports
If you noticed bugs, it would be very helpful that you report them, so I can fix them. Thanks!
Please mail bugreports to: [email protected]
A bugreport should look like this:
Name:
Device:
Date:
Version:
Things you done:
Title:
Description:
Any logs(logcat):
Any error codes:
---
Thanks to...
.. @loSconosciuto (the man who helped me to make it bootable!)
.. @SerkTheTurk
...Ubuntu community
...CyanogenMod community
...The Open Handset Alliance
...The Linux community
.. @safariking
.. @dhiru1602
... all testers (especially @xXPR0T0TYPEXx)
Source code
https://github.com/androthan/allto-device-legacy
https://github.com/androthan/allto-kernel-legacy
https://github.com/androthan/allto-vendor-legacy
Disclaimer
I'm not responsible for dead phones, dead sd-card or dead accesoires. You and only you decided to do these changes!
MrBrubble said:
CyanogenMod 7.2 for the Samsung Galaxy Player 3.6
Hello Galaxy Player community,
I finally compiled CM7 (Version 7.2) for our Galaxy Players 3.6.
Actually my build is not flashable, it's just an zip-file with the system, initramfs, bootstrap and more.
You can use this for developing or ROM porting.
This thread will be the development thread for CM7 on our devices.
MrBrubble
Feedback --> Answer this thread, thanks!
Support --> PM me
1. FAQs
2. Sources
3. Contents of zip-file
4. Downloads
5. Thanks to...
6. Disclaimer
1. FAQs
Q: Is this build flashable?
A: No, it isn't.
Q: Can I try to push the SYSTEM folder from the zip to my device?
A: Yes, but I can't guarantee that it will work, in worst case, just reflash the stock rom with ODIN.
Q: Is this for the EU or US version of the YP-GS1?
A: I think it will work on both, but I took the specs from an EU device.
Q: How long does it took to build it?
A: It took 2 months.
Q: Are the proprietary files already included?
A: Yes, they are.
2. Sources
Samsung OSRC: opensource.samsung.com
Device tree: github.com/team-hurricane-xda/android_device_cm7_aalto
CyanogenMod: github.com/CyanogenMod
3. Contents of the zip-file
There 4 folders in the zip-file:
BOOT: This is were the ramdisk files are stored. If you don't know what a 'ramdisk' is, just google it.
RECOVERY: This is the ClockworkMod custom recovery.
SYSTEM: This is the /system folder which contains CyanogenMod
OTA: Just some unneccessary files, ota-keys, manifest and more.
4. Downloads
Version 1: Uploading... (Sorry, my internet connection is very very slow)
5. Thanks to...
...SerkTheTurk for helping me, I hope his CM7 build for the 4.2 will be finished soon
...Samsung and TI for this great hardware
...The OpenHandsetAlliance for their great Android
...CyanogenMod for their great CustomROM
6. Disclaimer
I'm not responsible for bricked devices or dead sd-card. You and ONLY you decided to do these changes!
Click to expand...
Click to collapse
Good job
To safariking
safariking said:
Good job
Click to expand...
Click to collapse
You're welcome. It was (and may is) a lot of wotk.
Good work! Is this complete cm7?
Sent from my YP-GI1
Wow... There are really nice people who do all this hard work for free just for giving people some things that for them are impossible in other way...
I think that the less we can do is to say thank you and congratulations MrBubble (and all the people working on it)!
Enviat des del meu YP-G70 utilitzant Tapatalk 4 Beta
To SerkTheTurk
SerkTheTurk said:
Good work! Is this complete cm7?
Sent from my YP-GI1
Click to expand...
Click to collapse
Yes, it is a complete CM7 build.
Solution for libcamera.so:
1. Download this: https://github.com/galaxyishere/android_vendor_samsung_galaxysl
2. Replace "galaxysl" in the files in the root directory with "hugo" (galaxysl-vendor.mk, galaxysl-vendor-blobs.mk and BoardConfigVendor.mk)
3. Replace the files in the dir called proprietary with the files from a system dump from your player 4.2 (You will find the files in: /system/vendor, /system/lib, /system/bin and /system/firmware)
4. Make directory: <cm7source>/vendor/samsung/hugo
5. Copy the files there
6. Try building, GOOD LUCK!
MrBrubble
Are there any bugs?
Sent from my YP-GI1
SerkTheTurk said:
Are there any bugs?
Sent from my YP-GI1
Click to expand...
Click to collapse
Yes, it's the first build.
MrBrubble said:
Yes, it's the first build.
Click to expand...
Click to collapse
Maybe you can list some of the bugs?
Sent from my YP-GI1
SerkTheTurk said:
Maybe you can list some of the bugs?
Sent from my YP-GI1
Click to expand...
Click to collapse
This is a dev thread. He doesn't have to list bugs.
But if I were guess, I'm gonna say everything from WiFi to camera, to Bluetooth and etc
Sent from my Amazon Kindle Fire using Tapatalk 4 Beta
goldflame09 said:
This is a dev thread. He doesn't have to list bugs.
But if I were guess, I'm gonna say everything from WiFi to camera, to Bluetooth and etc
Sent from my Amazon Kindle Fire using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah I understand but people would have a better understanding if they wanted to flash this. Also people could contribute to his device tree, knowing the bugs that they would fix
Sent from my YP-GI1
SerkTheTurk said:
Yeah I understand but people would have a better understanding if they wanted to flash this. Also people could contribute to his device tree, knowing the bugs that they would fix
Sent from my YP-GI1
Click to expand...
Click to collapse
You didn't read this:
MrBrubble said:
1. FAQs
Q: Is this build flashable?
A: No, it isn't.
Click to expand...
Click to collapse
You have to build it
Sent from my Amazon Kindle Fire using Tapatalk 4 Beta
goldflame09 said:
You didn't read this:
You have to build it
Sent from my Amazon Kindle Fire using Tapatalk 4 Beta
Click to expand...
Click to collapse
My bad I missed that
Sent from my YP-GI1
Downloading now will see what i can do
Okay i made a flashable zip file but it is not booting i think because it is missing the Boot.img file because it has no kernel now!!!
You need to compile a good kernel first before we can actualy try it out Thanks!!!
If you have a good kernel that is compitable with CM7 and our device i can modify the updater-script to let it install the kernel to then we can see if it will boot up!
PS:
This is maybe a better logo for your thread:
http://img341.imageshack.us/img341/4048/ubdb.jpg
To safariking
safariking said:
Downloading now will see what i can do
Okay i made a flashable zip file but it is not booting i think because it is missing the Boot.img file because it has no kernel now!!!
You need to compile a good kernel first before we can actualy try it out Thanks!!!
If you have a good kernel that is compitable with CM7 and our device i can modify the updater-script to let it install the kernel to then we can see if it will boot up!
PS:
This is maybe a better logo for your thread:
http://img341.imageshack.us/img341/4048/ubdb.jpg
Click to expand...
Click to collapse
Thanks for trying, I will upload a boot image (boot.img) now and post it in the OP.
MrBrubble
So we just need someone to build a flashable zip based on this ROM right?
Sent from my air conditioner unit running CyanogenMod
@MrBrubble I think if you compiled using 'make otapackage' it would've made a cwm flash able zip by itself
Sent from my YP-GI1 using Tapatalk 2
I tried but it said "no rule to make otapackage" :/
Sent from my YP-GS1 using xda app-developers app
MrBrubble said:
I tried but it said "no rule to make otapackage" :/
Sent from my YP-GS1 using xda app-developers app
Click to expand...
Click to collapse
I've researched the problem with trying to make otapackage and apparently you need to include recovery before starting the build. I'm not sure how to include it but I'm pretty sure it's in BoardConfig.mk, something along the lines of 'TARGET_NO_RECOVERY := false' but then again I'm not quite sure, and btw did you include a prebuilt kernel?
Yeah we need a flashable zip for this to work otherwise it is useless thanks anyways if you need help PM me!
Sent from my awesome S2 Plus

(ROM)(08-05-15)(UNOFFICIAL)(4.4.4)CyanogenMod 11.0(GPL)(HYBRID)

Please Observe the Note about Gapps/Recoveries in the Downloads Section.
GSM'rs Please read message 1977 BEFORE complaining about SMS Texting. Thanks​
{
"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"
}
CyanogenMod 11.0 is a free, community built distribution of Android 4.4 (Kit Kat) which greatly extends the capabilities of your phone and increases performance and reliability over "stock Android" for your device.​
Code:
* Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* 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 us for
* messing up your device, we will laugh at you.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked near the bottom of this post is a package that has come from another Android project that restores the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.​
Features:
CM11.0
Koush's SuperUser as default (built in)
Android KitKat 4.4.4
Root
Apollo
CM's "File Manager"
cLock Widget
Quick Settings Panel
Swipe option for Quick Settings
Quick Pull-down option for Quick Settings
Notification Drawer Quick Access Ribbon
New CM Wallpapers
Theme Engine
Scroll typed text with vol -/+
Multi Language Support
Whisper Push
Zipaligned
All images optimized
Whats Working:
Alarm/Clock/Countdown Timer/Stop Watch
Audio (alarm, music, ringtones, ui)
Automatic Screen Rotation
Battery Stats
Bluetooth Calling and Streaming
Bluetooth Tethering
Camcorder - see below
Camera
Count Down Timer
Data (3g/4g LTE)
Data Transfer Arrows
Developer Options
Display (for the most part. See not working for further details)
Exchange E-Mail
Google Sync: Account/Calendar/Contacts
Gallery
Google Voice Typing
GPS
Hangouts (Gtalk replacement)
HD Video Playback
LEDs
Mms (sending/receiving)
Performance Controls
Phone (making/receiving calls)
ScreenShot
Security (Blacklisting /Privacy guard /Screen Lock)
Signal Bars and dBm signal strength
Simultaneous Voice and Data
Sms (receiving /sending)
Sms messaging via hangouts (new integrated sms ability)
Sound Recorder
Stereo Sound Headphones (some static present when screen comes on and goes off)
Stereo Sound (rear speaker)
Storage (external /internal)
Superuser
Swipe Keyboard and Auto Correct
Terminal Emulator
Torch/Torch Toggle
USB Mass Storage (Access via pc connection): External /Internal
USB Tethering
Vibration (calls , haptic feedback, notifications)
Vibrator Intensity settings
Video Chat (ie: Skype, Hangouts, etc.)
Video Playback (Youtube, Camcorder)
Voice Dialer
Voice Search
Live Wallpapers /Wallpapers
Weather from network location
Widgets
WiFi
WiFi Hot Spot (native WiFi tethering)
Youtube App/streaming video
What's Not Working:
Netflix: However, there is a workaround for this via use of the Xposed module: [Xposed][HACK] Workaround for Netflix This was discovered by member @hochoch. Thanks be to him. I have attempted to place the install instructions here. However, IF you feel confused please refer to the Workaround site.
To install:
Download and Install the Xposed Installer APK http://dl.xposed.info/latest.apk.
... > move to the dir containing the file
... > adb install de.robv.android.xposed.installer_v32_de4f0d.apk
You will be asked if you will allow this. Say yes.
Switch to the phone and the app directory. Install the Xposed framework:
... Find Xposed Installer... Tap it... Tap Frameworks... Tap ok... Tap Install/Update...
. . select Remember choice forever... Tap Allow... Tap ok to ReBoot
Download and Install the APK linked in this post: linked apk
... > move to the dir containing the file
... > adb install XposedCM10.1NetflixWorkaround.apk
Startup the Xposed Installer... Tap Modules.. Tap the check box.. Tap ret key twice
After enabling the module in Xposed Installer ... Reboot your phone. Enjoy Netflix.
If your PC hangs on one of the adb install commands... look at your phone and Tap the OK.
And this works on our CM11.0 (4.4.4) xposed-framework
Click to expand...
Click to collapse
Bluetooth Calling: It's hit or miss. Either doesn't work for some, or has bad quality for others.
Bluetooth will NOT "turn on" our ReZounds. Hardware is not designed for it. In order to make a "Hands free call" you must at least "Activate" the phone. Only has to show the "Lock Screen". Then your Bluetooth must be of the type that has a "Button" you can press to activate voice calling. Mine is a Plantronics Pro and the sequence goes like this:
Naturally your Bluetooth and phone have to be paired.
Push Power Button on Phone.
Push or Press your Bluetooth button.
Listen for command request.
Recite the name in your call list you desire to call.
Hope that the voice to text translation was correct...
MHL/HDMI: This most likely will never work on AOSP and should be considered a "don't hold your breath"
Camcorder: Built in one will scramble the pic IF started in portrait mode. Horizontal mode works ok. However, in both modes you can only get 3 video saves and then you have to reboot to get another 3. Repeat.
Installation InstructionsI recommend users of this rom to be on the latest firmware and Hboot with an s-off device. If you are not on the latest global firmware: Here or Here.
NOTE: For recovery I use CWM Touch 6.0.3.6 but you can also use TWRP. Some wipe options below may not be included in other recovery options. Still wipe what is available the best you can.
1. Put the Rom on the root of your SD Card
2. Compare MD5 Sum
Windows: MD5 Calculator
LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
Mac: Open a terminal and type: md5 [path to the rom on your sd card]
3. Reboot to Recovery
4. Scroll down and select "Wipe"
5. Wipe the following:
Wipe ALL data/factory reset
Wipe /data
Wipe /cache
Wipe Dalvik-cache
Wipe /boot
Wipe /system
Optionally wipe:
Wipe battery stats
Wipe rotate settings​6. Scroll to and press return
7. Install Rom from SD Card
8. Reboot and enjoy!
​Further questions about the ROM
Please check the FAQ in the second post.​
Note: Please do not mirror the Rom. Thanks.​NOTICE: I do not provide a changelog. However, you may view the official CM changelog by clicking CHANGELOG (Not yet available for cm-11.0)​​To those complaining about Battery usage, please view message: 2429
The Battery tests have been updated: Sep 7th, 2014​Downloads:
ROM: DOWNLOAD
----------------------------------------------------------------------------------------
4.4.4 GApps: gapps-kk-20140620-signed.zip
4.4.4 BaNkS GApps: GApps from BaNkS
4.4.3 GApps: gapps-kk-20140606-signed.zip
4.4.3 BaNkS GApps: GApps from BaNkS
​Check out the message 2322 for a proper TWRP and CWM to install the "Standard" Gapps.​
Thank You to the following individuals for their heavy involvement in making Kit Kat possible for the HTC Rezound and for their continued efforts to improving the platform (in Alphabetical Order):
Flyhalf205 -Donate
kkozma - Donate
_litz - Donate
REV3NT3CH - Donate
Snuzzo - Donate
TheBr0ken - Donate​Source:
Google - Android
Cyanogen - Source
Vigor - Beta builds
Vigor - Kernel
Please note that CM-11.0 is super fresh and no where ready for prime time action. However, it is stable enough to use daily. Over time, the CyanogenMod team will add back features that are currently missing and adding some never before available as development continues.
Please see post two for additional notes.​
Frequently Asked Questions
HTC Rezound UNOFFICIAL CM11.0 (KK-4.4.4)​
This is a short list of Q&A that should help you find answers to the questions you might have concerning flashing and using this ROM.​
[SIZE=+1]Q1: What version of Android is this?[/SIZE]
This Rom is CM11.0 which is currently built on Android 4.4 "Kit Kat"​
[SIZE=+1]Q2: Lost root?!? Built in Superuser doesn't work?[/SIZE]
Go into Developer options and change Root access to "Apps and ADB"​
[SIZE=+1]Q3: Is this ROM S-On compatible?[/SIZE]
By default, no. Follow these instructions to flash on an S-On device:
NOTE:
You must have the Android SDK downloaded and installed onto your computer.
You must be familiar with the SDK's install directory structure.
You must be familiar with using terminal and know how to cd to the platform-tools folder of the Android SDK's install directory.
1. Open the Rom zip with an archive tool such as 7zip and extract the boot.img from it.
2. Place the boot.img into the platform-tools folder of the Android SDK's install directory.
3. Put the Rom and GAPPS on the root of your SD Card
4. Compare MD5 Sum
Windows: MD5 Calculator
LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
Mac: Open a terminal and type: md5 [path to the rom on your sd card]
5. Reboot to Recovery
6. Scroll down and select "Wipe"
7. Wipe the following:
Wipe ALL data/factory reset
Wipe /data
Wipe /cache
Wipe Dalvik-cache
Wipe /boot
Wipe /system
Optionally wipe:
Wipe battery stats
Wipe rotate settings
Click to expand...
Click to collapse
8. Scroll to and press return
9. Install Rom and gapps (in that order) from SD Card
11. Return to the main menu of the recovery and select "Developer Menu".
12. Select "Reboot to bootloader
13. Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
14. Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
15. Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
16. Watch the output of the terminal, it should say something like "sent successfully".
17. Finally send this command:
Code:
fastboot reboot
This command reboots your device into Android. Wait for it to boot up and enjoy your new freshly installed CM10.12
Note: If you are having issues connecting your device to your windows computer in fastboot, please insure the drivers are up to date by installing the latest version of HTC Sync for the Rezound.​
[SIZE=+1]Q4: Where did the Developer options in settings go?[/SIZE]
Google/Android has hidden this feature in JB 4.x+ and up. Follow these steps to re-enable the feature:
Go to settings > about phone. Tap Build Number 7 times. Tapping Build Number 7 times re-enables the Developer Options in settings.​
[SIZE=+1]Q5: Where did the reboot menu go?[/SIZE]
In Android 4.4 this menu is hidden by default in CM11.0 and must be enabled.
Step 1: Enable Developer options using the method described in Q4.
Step 2: Go to Developer options and check the Advanced reboot box.
Step 3: Go to System settings > System > power menu. Insure the Reboot menu box is checked.
Click to expand...
Click to collapse
[SIZE=+1]Q6: What is the recommended HBOOT and Radio for this ROM?[/SIZE]
RADIO: 2.23.10.0123r, 2.23.10.0124r
HBOOT: 2.28
Click to expand...
Click to collapse
If your device is not using this firmware and HBOOT, its very simple to update. Just follow the guide [URL=" http://forum.xda-developers.com/showthread.php?t=2509770 [/URL] to get updated.​
[SIZE=+1]Q7: Is this ROM GSM compatible?[/SIZE]
Yes. You must enter Mobile Networks and change preferred network list to GSM.​
[SIZE=+1]Q8: Why isn't my WiFi working?[/SIZE]
You're most likely s-on then. You must flash the boot.img that comes with the .zip inside of fastboot.​
[SIZE=+1]Q9: What recovery is recommended?[/SIZE]
ClockworkMod 6.0.3.6 or higher... TWRP 2.6.0.1 or higher...​
[SIZE=+1]Q10: I can't mount my phone to my computer as a mass storage device. How can I manage my internal/external storage with my computer?[/SIZE]
If you have the most recent HTC drivers installed and are still experiencing issues, reboot into your recovery, and try mounting your storage that way. If you are still having issues, try a different cable, USB port, or computer. Lastly, try to avoid using an external USB hub. Those may cause issues, as well.​
Please be smart and use the search bar first before posting any questions...​
【ROM】【4.4.4】【UNOFFICIAL】CyanogenMod 11.0【06-30-14】【GPL】【HYBRID】
Reserved
Thank you!!
Flashing with twrp is ok?
Sent from my ADR6425LVW using Tapatalk
For those of you who wish to contribute to it's progress and may not be as code or tech savvy, feel free to look over the things that are "untested" in post number 1 and let the rest of us know if it works or not!
This helps a lot so thank you.
-Neo
bbgreen said:
Thank you!!
Flashing with twrp is ok?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I believe so. Although I'm unsure of what version may/may not be compatible as I do not use it. FlyHalf would be the best person to answer this.
IAmTheOneTheyCallNeo said:
I believe so. Although I'm unsure of what version may/may not be compatible as I do not use it. FlyHalf would be the best person to answer this.
Click to expand...
Click to collapse
I use 2.6.3.0 with no issues
kkozma said:
I use 2.6.3.0 with no issues
Click to expand...
Click to collapse
as i used 2.6.3.3
I want to try it so bad, but I need the browser and camera... I'll wait until it's awesome!
Sent from my Rezound using Tapatalk
I used 2.6.3.0 from here : http://goo.im/devs/OpenRecovery/vigor
Just make sure you properly wipe/etc if doing a clean install, and after any "dirty flash", wipe dalvik and cache before you reboot.
Is this ion based?
Sent from my ADR6425LVW using Tapatalk
mavpts said:
Is this ion based?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
No
---------- Post added at 09:00 PM ---------- Previous post was at 08:51 PM ----------
For any and all gsm users installing this...there is a few trick to get things working and we are still working on this. I may also do my best to release a pure gsm version of 4.4 for our device
does art work or are we to stay on dalvik?
PMEM vs. ION
mavpts said:
Is this ion based?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Forgive my ignorance on this one, but I simply don't know enough about it to reason this out for myself. Can you guys get an ION version booting? The reason I ask is because I remember the reason you guys stuck with PMEM was because you still had the ability to use the camera/camcorder with that type of memory management. Would building with ION alleviate any of the existing problems since that's more or less the direction that Android wants to take memory management? I'm sure you guys had already thought of all of this, just curious if there was any advantage in trying to get it built with ION (and admittedly it's a selfish "want to know" on by behalf). Congrats and thanks to Fly, Litz, Rev, Neo, KKozma, TheBroken and everybody else responsible for getting this done. It's been awesome to watch you guys work.
Also Bluetooth streaming works. Not sure about bluetooth calling though.
I don't think any of us have tried ion with cm11 yet. I did build cm10.2 ion and it boots, but the camera doesn't work at all.
That said, I am going to give the old college try on using a different display hal for cm11 which requires ion. There's a very small chance it could help with the camera, but don't hold your breath.
iamwalterwhite said:
Forgive my ignorance on this one, but I simply don't know enough about it to reason this out for myself. Can you guys get an ION version booting? The reason I ask is because I remember the reason you guys stuck with PMEM was because you still had the ability to use the camera/camcorder with that type of memory management. Would building with ION alleviate any of the existing problems since that's more or less the direction that Android wants to take memory management? I'm sure you guys had already thought of all of this, just curious if there was any advantage in trying to get it built with ION (and admittedly it's a selfish "want to know" on by behalf). Congrats and thanks to Fly, Litz, Rev, Neo, KKozma, TheBroken and everybody else responsible for getting this done. It's been awesome to watch you guys work.
Click to expand...
Click to collapse
As this is still very new even to the cyanogen source...many things are still being pushed to cm11 as well as commits...it will all be ironed out in PMEM soon...ION will take some time
Doh. Stupid double post
So far so good, usb tethering works, alarm, stopwatch and countdown timer work as well.
i have noticed if i change runtime to art i get fc of gmail, gapps and a few other apps, it is in a loop to so only fix was to turn back runtime to dalvik.
other than that keep up the great work! all the devs here are a joy to be apart of this community
update - Also i have been a rom toolbox user since the beginning and it has always worked, but in this rom i am unable to uninstall apps, i can freeze them tho, just thought id share
mavpts said:
Also Bluetooth streaming works. Not sure about bluetooth calling though.
Click to expand...
Click to collapse
Blue tooth calling works.
Sent from my ADR6425LVW using Tapatalk

[ROM][Unofficial_SlimLP][Quincyatt][BETA]

{
"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"
}
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimLP is the project name for SlimRoms based on Android 5.0 Lollipop and offers the following original features:
Slim Dialer
A full replacement of the official Google closed source dialer with added features. - We've got you covered.
Privacy guard
Disable unnecessary permissions set by app developers. - Privacy is part of the experience.
Slim Center
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticons..etc. - You'll be tapping away to your heart's content.
Custom Shortcuts WIP
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - Customize it the way you like it.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
--------------------------------------
Instructions:
Recovery: use my TWRP 2.8.1.0 recovery.
Make sure you're on the UCMD3 radio
Format /system, /data and /dalvik
Flash the ROM
It's recommended to reboot and let it settle!
Reboot to recovery
Flash GApps if desired
Reboot​
ROMS​
Slim-quincyatt-5.1.1.beta.0.9-UNOFFICIAL-20151010-1515.zip​
GAPPS​
Gapps​
What works?
RIL
MMS
Camera
Video Recording and Playback
What doesn't work?
1080P video recording
flashlight
you tell me?
USE_ONLY_THIS_UNOFFICIAL_TWRP!!!!!​
TWRP 2.8.3.0​
I tried the 0221 build and had the wake issues. I'm gonna try the 0342 build and see if that does it! I've been experimenting building kernals for the S3 and XT912 to learn! I'm gonna start working on the I717 tonight and see if I can help everyone out! And thanks again for all of the hard work gimmeitorilltell!
Sent from my DROID SPYDER using XDA Premium 4 mobile app
SgtTeabag said:
I tried the 0221 build and had the wake issues. I'm gonna try the 0342 build and see if that does it! I've been experimenting building kernals for the S3 and XT912 to learn! I'm gonna start working on the I717 tonight and see if I can help everyone out! And thanks again for all of the hard work gimmeitorilltell!
Sent from my DROID SPYDER using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, the 342 seems to work, but also has wake issues after a while. And looking forward to testing your Kernals :good:
Will try NOW and use it from tomorrow daily driver to test from MIUI!
[ Updated! ]
1. Updated to TWRP 2.8.1.0 recovery.
2. Not sure for i717 => 'UCMC1 radio"
3. Tried Both builds
Slim-quincyatt-5.0.2.alpha.0.91-UNOFFICIAL-20150202-0342.zip
Slim-quincyatt-5.0.2.alpha.0.91-UNOFFICIAL-20150202-0221.zip
=> Keep rebooting as soon as it boots to home screen after you click "power" button to turn off and try to wake up back.
Still it was enough excitement feeling to see the LP home screen on i717!
Hope we could see working build soon.
P.S. Can any developer could also change PIT(partition modification original 2GB limit) specially for new build?
pointdooly said:
Will try NOW and use it from tomorrow daily driver to test from MIUI!
[ Updated! ]
1. Updated to TWRP 2.8.1.0 recovery.
2. Not sure for i717 => 'UCMC1 radio"
3. Tried Both builds
Slim-quincyatt-5.0.2.alpha.0.91-UNOFFICIAL-20150202-0342.zip
Slim-quincyatt-5.0.2.alpha.0.91-UNOFFICIAL-20150202-0221.zip
=> Keep rebooting as soon as it boots to home screen after you click "power" button to turn off and try to wake up back.
Still it was enough excitement feeling to see the LP home screen on i717!
Hope we could see working build soon.
P.S. Can any developer could also change PIT(partition modification original 2GB limit) specially for new build?
Click to expand...
Click to collapse
After Exact Step of flashing, I could load 0342 firmware without reboot issues.
1. Factory Data reset
2. Wipe Cache/Dalvik
3. Format System/Data
4. Install SlimFast zip from Sdcard
5. Wipe Cache/Dalvik
6.Reboot device
7.boot back into recovery
8.Wipe Cache/Dalvik
9. Flash gapps
10.Wipe Cache/Dalvik
11. Flash SuperSU
12.Wipe Cache/Dalvik
13. Reboot
Wow! It is really working LP except except internal & external sd cards which is important.
=> Can't use camera and video camera at all since it can't save to internal SD.
When you open camera app, you will receive this errir "Camera app says "Insert an SD card before using the camera"".
everything seems to work fine but no audio
kukke5 said:
everything seems to work fine but no audio
Click to expand...
Click to collapse
pointdooly said:
After Exact Step of flashing, I could load 0342 firmware without reboot issues.
1. Factory Data reset
2. Wipe Cache/Dalvik
3. Format System/Data
4. Install SlimFast zip from Sdcard
5. Wipe Cache/Dalvik
6.Reboot device
7.boot back into recovery
8.Wipe Cache/Dalvik
9. Flash gapps
10.Wipe Cache/Dalvik
11. Flash SuperSU
12.Wipe Cache/Dalvik
13. Reboot
Wow! It is really working LP except except internal & external sd cards which is important.
=> Can't use camera and video camera at all since it can't save to internal SD.
When you open camera app, you will receive this errir "Camera app says "Insert an SD card before using the camera"".
Click to expand...
Click to collapse
All the issues we're having with this lovely rom, @gimmeitorilltell is trying to fix. We have to wait for the next update. Hopefully @SgtTeabag has a Kernel for us to fix some of the issues
New build in OP! Wake lock issues squashed! Still no audio! Videos play except 1080, camera works... Slim-quincyatt-5.0.2.alpha.0.91-UNOFFICIAL-20150202-2324.zip
New BUILD with Audio
OP has it with audio, video recording & playback!
following your progress with great interest! Thanks again.
installation went without a hitch.
i used cwm 6.0.4.3
i wasn't able to setup an apn.
the screen said that the apn settings are not available for this user.
tried to add them anyway but wouldn't save.
gimmeitorilltell said:
OP has it with audio, video recording & playback!
Click to expand...
Click to collapse
Baseband isnt working
---------- Post added at 11:35 AM ---------- Previous post was at 11:32 AM ----------
beenkenobee said:
installation went without a hitch.
i used cwm 6.0.4.3
i wasn't able to setup an apn.
the screen said that the apn settings are not available for this user.
tried to add them anyway but wouldn't save.
Click to expand...
Click to collapse
Is your baseband working ?
TeamAndroid14 said:
Baseband isnt working
---------- Post added at 11:35 AM ---------- Previous post was at 11:32 AM ----------
Is your baseband working ?
Click to expand...
Click to collapse
nope
TeamAndroid14 said:
Baseband isnt working
---------- Post added at 11:35 AM ---------- Previous post was at 11:32 AM ----------
Is your baseband working ?
Click to expand...
Click to collapse
beenkenobee said:
nope
Click to expand...
Click to collapse
Thanks for the heads up. I do not have an active sim card for my device so I never thought to checkout the baseband. I'll see what I can find.
My device is on UCMD3 version.
gimmeitorilltell said:
Thanks for the heads up. I do not have an active sim card for my device so I never thought to checkout the baseband. I'll see what I can find.
Click to expand...
Click to collapse
@gimmeitorilltell , Thanks brother, I think the audio isnt working still, im not sure if its my phone.
gimmeitorilltell said:
Thanks for the heads up. I do not have an active sim card for my device so I never thought to checkout the baseband. I'll see what I can find.
Click to expand...
Click to collapse
Don't know if this helps, but no audio or baseband on Validus or Broken either.
Sent from my SM-T310 using XDA Premium 4 mobile app
TeamAndroid14 said:
@gimmeitorilltell , Thanks brother, I think the audio isnt working still, im not sure if its my phone.
Click to expand...
Click to collapse
dparrothead1 said:
Don't know if this helps, but no audio or baseband on Validus or Broken either.
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have audio on my device, can you all confirm whether you do or don't?
gimmeitorilltell said:
I have audio on my device, can you all confirm whether you do or don't?
Click to expand...
Click to collapse
I am on the 342 build...it has no audio of any kind.
Sent from my Nexus 6 using XDA Premium 4 mobile app

Categories

Resources