Related
CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
cyanogen said:
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Click to expand...
Click to collapse
Visit the CHANGELOG for a full list of changes and features!
All source code is available at the CyanogenMod Github!
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance (howto).
INSTRUCTIONS:
- First time flashing CM 6 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery (Unrevoked method is recommended).
2. Do a Nandroid backup!
3. Update your radio! New radio from 2.2 roms is required, see downloads below.
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Go into recovery and dump the "/proc/last_kmsg" file.
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get send the full output.
- Pastebin links preferred
- Please use the issue tracker whenever possible!
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
This is the latest release candidate so any and all feedback is appreciated!
The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.
GSM
Latest version: 6.1.1-Desire - 16/12/2010
Download: update-cm-6.1.1-Desire-signed.zip
Also available for download via ROM Manager
MD5Sum: e14b66d1e24f34603e2aaf071f20c5e2
CDMA
Latest version: 6.1.1-BravoC - 12/16/2010
Download: update-cm-6.1.1-BravoC-signed.zip
Also available for download via ROM Manager
MD5Sum: 5bd096950c505742e9e84fb6dc1da5e3
Google Addon: HDPI-20101114
Download: http://goo-inside.me/google-apps/
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
Rooting Guide
http://forum.xda-developers.com/showthread.php?t=788044
Google Addon: latest HDPI-20101114
Other release http://goo-inside.me/google-apps/
Radio Firmware: 5.x radio required (GSM ONLY)
Desire GSM radio thread
Read/Write Access System Partition (S-OFF)? (GSM ONLY)
Thank's to AlphaRev [site] [xda]
Low storage for apps? (GSM ONLY)
Flash the AlphaRev HBOOT Bravo N1Table (Require S-OFF)
Follow this instrunction for update without data lost (aka no data wipe)
Still low storage for apps?
Install an A2SD solution: Firerat or Darktremor
i recommend the Firerat solution: CM specific, less space usage 25kb vs 6mb, bind mount, no boot loop, auto restore after cm rom update (from 1.35b)
No audio on FM Radio? (GSM ONLY)
http://forum.xda-developers.com/showpost.php?p=8992389&postcount=1280
Change Provider Name? (CDMA ONLY)
http://forum.cyanogenmod.com/topic/9101-guide-change-provider-name-in-cm6/
Adfree symlink instruction
can you post screes??
Woot, downloading now!!!
WAHEYYYYYYYYY! I'll flash asap. Do we have old school a2sd yet?
Sent from my HTC Desire using XDA App
GANJDROID said:
WAHEYYYYYYYYY! I'll flash asap. Do we have old school a2sd yet?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
No. Old school A2SD is aimed for CM 6.1. Just be happy with the ROM as it is atm. It's great. It's phenomenonal, marvellous, beautiful... amazing... [SteveJobsMode=off]
oleeeeeeee...thanks cyanogenmod team...
is the cyonegen mod soo good? or way are all so happy??
i flash it ... ext3 needed?
yasars said:
is the cyonegen mod soo good? or way are all so happy??
i flash it ... ext3 needed?
Click to expand...
Click to collapse
Besides JesusFreke, cyanogen is the godfather of Android.
CM exists since the G1/HTC Magic. After cyanogen got his Nexus, the project started to grow big. Atm it's (officially) available for 8 devices with many other unofficial ports for other devices.
No ext partition on the SD card is needed, it uses the Froyo A2SD implementation.
great man!!!!!
I just felt a little bit afraid...
I flashed all the things as you said ( Radio, wipe, CM, Gapps) then reboot...
I was stuck on a little Android robot just close to a white box and a yellow arrow going out the bof and going towards the robot..
Remove my battery 2 times than nothing...
Now, I wait a little bit more, then some stranges things happened ( going to HTC logo, reboot, the box and the android, reboot) and now, I have the boot animation...
All seem correct, but I was so afraid
profete162 said:
I was stuck on a little Android robot just close to a white box and a yellow arrow going out the bof and going towards the robot..
Remove my battery 2 times than nothing...
Click to expand...
Click to collapse
When you see that the radio is being flashed, it's a VERY bad idea to pull the battery at that point!
Ok, I didn't know that!
So I feel lucky, everything is fine!
Thank for the information, I won't do that again!
just flashing with a2sd.
Fingers crossed it still works
update: It works with a2sd!!
I hope it dont cause problems as that a2sd method was for the nightlys.
Has the bootimage been changed since the last nightly?
Screens please
Sent from my HTC Desire using XDA App
Restored nearly 30 apps and space is 102Mb to 69Mb. This is normal? İ checked apps and all of them on SD card.
Sent from my Desire using XDA App
Static IP with DHCP router
Hi
I still have problem with connecting wifi to a DHCP router. I tried Wifi Static to set statis ip which worked fine on the other rom, but i have never been able to use it in CM Rom
Besides, I have two APN on my 3 Network, but I can only choose 1 of them hence I cannot swap to the other one.
I'm looking for helps from everyone
Thank you.
I don't understand why you people want screenshots... it's stock Froyo in appearance, other than some blues swapped for cyans.
Can't wait to flash this. Kudos to the CyanogenMod team for all their hard work.
Is wifi sleep issue fixed?
Is vpn issue fixed?
Is that definitely the correct md5 of the Radio image?
I get:
Code:
e75698d9341820818dc7f345f48717cf
Consistently, downloaded both on-device using wget and on my PC using Chrome and wget.
[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project
CyanogenMod is a free, community built distribution of Android 5.1 which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
XDA:DevDB Information
[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project, ROM for the Sony Xperia Z3 Compact
Contributors
jerpelea
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-12-02
Last Updated 2015-04-13
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
ENJOY AN UNOFFICIAL CM RELEASE BROUGHT TO YOU BY FreeXperia Team
PLEASE DONT MIRROR OUR ROMS
Homepage
www.freexperiaproject.net
thanks to all who made this possible supporting us
contributing with code, donations or even trusting us
thanks to SONY that made all this possible !
the build should be here soon: http://fxpblog.co/cyanogenmod/cyanogenmod-12/
we have enabled daily builds
if your device is not yet in the list will appear soon (1 day,1 week, 1 month) no ETA please
but you have to remember that is an early alpha build
Thread closed until there is a build available
Thread cleaned
@jerpelea, please PM a mod or report this post to get the thread re-opened immediately.
Now that the daily builds are continued, have you or any other dev worked on CM12 for our device?
I am currently able to compile, but there seems to be a couple of issues that users are reporting,
Problems with com.qualcomm.location.apk
Updater script errors in recognizing proper device
System bootloops after 'starting apps'
Code:
E/installd( 269): DexInv: --- END '/system/priv-app/com.qualcomm.location/com.qualcomm.location.apk' --- status=0x0100, process failed
D/AndroidRuntime( 4634): Shutting down VM
E/AndroidRuntime( 4634): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
It might be that I am not importing all the necessary repositories or the wrong ones (in my local manifests),
I would be grateful if device specific repos can be mentioned in the OP or second post
Thank you
Merry Christmas!
Can't wait for my Z3C build to be available.
AlexBurnout77 said:
Can't wait for my Z3C build to be available.
Click to expand...
Click to collapse
On that topic -- why has this been re-opened if there are still no builds?
@jerpelea can we get at least a vague explanation of what's halting the builds from being made/uploaded?
Exactly. If they wanted to give us a full working built they can. I dont understand why theyre dragging thier boots, unless they want to release lollipop stock first.
someone755 said:
On that topic -- why has this been re-opened if there are still no builds?
@jerpelea can we get at least a vague explanation of what's halting the builds from being made/uploaded?
Click to expand...
Click to collapse
g0ldenchild562 said:
Exactly. If they wanted to give us a full working built they can. I dont understand why theyre dragging thier boots, unless they want to release lollipop stock first.
Click to expand...
Click to collapse
The builds weren't being uploaded because the build server was down for a couple of weeks. Now that it's back up things should be getting back to normal.
They can't give us a full working build because the builds aren't fully working. Even with Sony sources and binaries the modem still isn't working, CM12 isn't fairing much better.
Gairtial said:
The builds weren't being uploaded because the build server was down for a couple of weeks. Now that it's back up things should be getting back to normal.
They can't give us a full working build because the builds aren't fully working. Even with Sony sources and binaries the modem still isn't working, CM12 isn't fairing much better.
Click to expand...
Click to collapse
Well then the thread sbouldnt have been reopened. If theres nk available builds yet...
Yeah I'm not sure why they reopened it when they're not doing CM12 builds.
Did anyone flashed first release? What's working and not working.
Using the build from the 28th
Confirmed not working & issues:
*cell service
*camera
*Brightness slider is finicky
*device gets VERY hot
*massive battery drain
Things that work on this CM rom but not the latest AOSP build:
*NFC
*sd Card Support
*USB mounting to a PC
* Location
Notes:
This installs the stock CM recovery so make sure to get rom and gapps installed via TWRP the first go.
I had to edit the updater-script to flash. Removed the first line of device checks as it saw mine as a aries and would not flash
PS, for the love of all things holy, please setup a mirror. The current provider is just shy of torture.
finally we get one build,will flash.wait for my report
edit:lol,saw it,plan is over
edit2:still flashed it,it seems we have baseband at least(not display unknown),on its first boot,i noticed it's searching signal,then disappeared,checked baseband not unknown,tried to search for carrier but it never ends.
did a logcat,before logcat I turned on airplane mode,after its beginning i disabled airplane mode,tried to search for operator,then turned it to lte mode then tried to search again.
https://www.dropbox.com/s/nfexgudos3bni87/1.txt?dl=0
I don't understand why two built on 28 december ? One 280Mo and an other 285Mo .
http://uploaded.net/f/4bbo69
You can see to the bottom one this page .
Thanks i'm very happy to see CM12 on this device
mick711 said:
I don't understand why two built on 28 december ? One 280Mo and an other 285Mo .
http://uploaded.net/f/4bbo69
You can see to the bottom one this page .
Thanks i'm very happy to see CM12 on this device
Click to expand...
Click to collapse
the other one is for z3.I think I didn't see more builds..
Just tried the latest renamed nightly for (z3c instead of aries)-
FXP-cm-12-20141228-UNOFFICIAL-z3c.zip
The WIFI radio seems to work - but the LTE and voice radio connects
right at boot and then disconnects and goes away.
On shutdown/restart the same thing happens - LTE/Voice connects at first
and then it goes away.
I saw funky radio issues when testing the pure AOSP aries builds-
so it may not be just the CM12 ROMS.
I also had to edit the z3c zip file to allow the aries product name
so I could install it from doomlord's stock CWM kernel recovery image-
but that was minor compared to the radio issues.
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
General:
These are UNOFFICIAL CM12.1 Lollipop Nightlies brought to you by Open Desire Project and TeamCodefire as a continuum to CM 11.0 and 12.0 builds. Builds are generated automatically on Mon/Wed/Fri/Sun. Process starts around 00:30 PST/PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Last 7 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
Mustaavalkosta
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
Open Desire Project
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies
Download gapps from here
Put the files on SD card
Reboot to recovery
Do factory reset (ie. format /system, /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-12.1-YYYYMMDD-UNOFFICIAL-saga.zip
Flash gapps zip
Remember to flash boot.img via fastboot if you have S-ON
Reboot and enjoy
Update instructions:
Download Nightlies
Put the file on SD card
Reboot to recovery
Flash cm-12.1-YYYYMMDD-UNOFFICIAL-saga.zip
Remember to reflash boot.img via fastboot if you have S-ON
No need to flash gapps as CM backuptool script should take care of them (results may vary depending on which gapps package you are using)
Reboot and enjoy
Kernel
Source: github
Compiler: stock AOSP gcc-4.8
Branch: cm-12.1
Kernel Version: 3.0.101
defconfig: saga_defconfig
Contact:
My Google+
#opendesireproject @ freenode
Donations:
For build server & hosting: codefi.re (use the donation button)
I don't really need your money right now but if you insist on donating to me I suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
Or I'm having other recovery issues.
A: Download and install the latest recovery here.
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: Hey, my old phone is running the latest Android version, i want to thank someone!
A: Press thanks button here
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM12.1 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm12.1
cd cm12.1/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-12.1/local_manifest.xml -O .repo/local_manifests/local_manifest.xml
repo sync
. build/envsetup.sh
lunch cm_saga-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/saga/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
Unofficial CyanogenMod 12.1 Nightlies, ROM for the HTC Desire S
Contributors
kylon, Mustaavalkosta, paulb_nl, Phantom Shadow
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Twrp 2.8.7.0
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-04-02
Last Updated 2017-01-04
Bugs / Not working stuff
headset mic in call
kylon said:
ffc camera
headset mic in call
Click to expand...
Click to collapse
Thanks, Kylon, Mustaavalkosta, Paunb_nl, and Phantom Shadow, for being active in supporting DS's community with up to date development. I am very appreciated your kind contribution. Thank you very much.
Writes
Not enough memory. Please delete minimum 250 mb...
I see in the settings is all right.
Phone has lags
Thank you so much!!!
EDIT: cyclic reboot
Lapyyyyyy said:
Writes
Not enough memory. Please delete minimum 250 mb...
I see in the settings is all right.
Phone has lags
Thank you so much!!!
EDIT: cyclic reboot
Click to expand...
Click to collapse
Yeah, I fell asleep before the build finished and I had chance to say the same here that I already said on the ace thread:
First build is now on the mirrors. Expect everything to be broken, be thankful for anything that works. There's no schedule for these nightlies yet as I haven't really had time to think how I'll juggle 3 different versions so they don't start compiling at the same time. New builds will come whenever I feel like making one until things settle down a bit and build schedule is decided.
Lapyyyyyy said:
Writes
Not enough memory. Please delete minimum 250 mb...
I see in the settings is all right.
Phone has lags
Thank you so much!!!
EDIT: cyclic reboot
Click to expand...
Click to collapse
Thanks, I got the same thing as you mention plus android keyboard FC. However, it is the first built, just booted up is alright. The rest is leaving for Mustaavalkosta to take care of. If DHD is working, DS should be working as well. Thanks for Mustaavalkosta hard work.
Hi Mustaavalkosta, CM-12.1-20150403-UNOFFICIAL-saga.zip faced the same issues as previous built, Android keyboard FC, not enough space for the system. There should be somethings wrong because the internal storage still has 1.03 GB available as well as my SDCard still has 14 GB available space. However, front camera is working on this built. I am wondering if it is possible to copy files related to camera from this built to CM-12 and which files should it be replaced. I am trying to produce logcat without success. I am sorry about that. Thank you very much for your great effort.
Thanks, Mustaavalkosta, I got the answer by replacing Camera2.apk from this built to CM-12 by installing using root explorer and front camera is now working on my device, CM-12 Rom.
kylon said:
ffc camera
headset mic in call
Click to expand...
Click to collapse
No, it is not. Front camera is working fine on CM-12.1. Thanks.
Can I perform update from CM12 to 12.1?
@qd42: Shouldn't be a problem since it's a minor Android update. But since this is in alpha state I'd suggest you wipe.
Same for me: "not enough space", keyboard FC on first boot (works good now in German). Front-camera works flawlessly. I'll be testing more.
Well, I'm tried to make update from CM12 and I don't reccommend to do this to others because of various system errors after boot like "android.process.acore errors".
How can i install this rom ?
I am using TWRP 2.8.5.2 as Recovery
I have swiped evertyhing i could on the phone
When i choose to install this ROM i get the Message: script succeeded result was /system
After flash boot.img, the Cyanogenmod-Logo still dont disappear after 10 Minutes ... (while booting)
€dit: Forget it. After 15 mins the Logo disappeared and the system has booted. But my SIM was not detected ...
€dit: SIM was detected ... but the phone tells me, i have less than 250mb free space ... wth ? I thought after a full wipe it should be at least 300mb free space ...
LuckyLoop said:
€dit: SIM was detected ... but the phone tells me, i have less than 250mb free space ... wth ? I thought after a full wipe it should be at least 300mb free space ...
Click to expand...
Click to collapse
It's a bug. As a temporary workaround remove /system/media/bootanimation.zip and warning should go away.
Mustaavalkosta said:
It's a bug. As a temporary workaround remove /system/media/bootanimation.zip and warning should go away.
Click to expand...
Click to collapse
Thanks MUstaavalkosta. So far, It is working fine. Flashed superSU v.2.48 beta makes it better. Ringtone is good, front camera is good. Just keyboad and google service have stop sign showed up some time. In fact they are still working. Thanks for your kind contribution.
I can't install any apps from the store get an error ’'-504''
Remove Boot animation before flashing as Mustaavalkosta suggested.
Okay,now that ive taken a break from studying,i can post a bug report on this. Accorrding to what ive seen,other than the known,solved ones,there are no other bugs. Much faster than 5.0.1 thats for sure. This is my new daily driver.
Sent from my SM-G900T using XDA Free mobile app
Hey guys, last time I flashed this the opposite side was not able to hear me upon my first call and the call quality was terrible when I returned the call after.
Of course I was in an area with good signal coverage.
Was this solved lately by any chance?
The space (LOL) problem is still unsolved. I believe that
Code:
55d502e msm7x30: use halfres bootanimation
was supposed to fix it.
vojtah1 said:
The space (LOL) problem is still unsolved. I believe that
Code:
55d502e msm7x30: use halfres bootanimation
was supposed to fix it.
Click to expand...
Click to collapse
How about without gapps? Works fine here on ace after that commit.
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
Installation Instructions
Make sure you have a second partition on your SD card formatted to ext4 before flashing!!!! This can be created with either CWM recovery or with TWRP. gparted on Linux should also work. If you "SD card not supported" try repartitionning. If you get "Encryption unsuccesful" then you need to format the second partition as ext4 (or f2fs, your choice).
If on a BML rom (stock-based GB)...
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. It will reboot a couple of times, don't be worried.
4. If you want gapps, reboot to recovery, wipe data+cache and install gapps.
5. If you want root, flash SuperSU whenever
If on an MTD rom (CM7 and all ICS+)
1. Reboot to recovery
2. Wipe data, dalvik/art cache, system, and cache partitions
3. Install zip
4. If you want root or Gapps, install them now.
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess.
Bluetooth only enables from the notification pulldown, not when you go directly to settings. It does work just fine afterwards though
If you're coming from either the last Lollipop build or the initial pre-release Marshmallow build, there is a bug in TWRP that will prevent flashing anything but the ROM. To get around this, please flash the Marshmallow zip, then reboot to recovery, and then follow the typical instructions.
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
If you come across a bug, feel free to let me know by posting in this thread. I will not be working non-stop on this project, but will try to fix bugs that affect me as this is still my main phone (out of choice, not necessity).
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Taking pictures
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Video Recording
Automatic Brightness
Encryption
Compass
GPS
Headset Buttons
Semi-Working
Powered-off charging animation - works at first, but then stops working. Seems to be an Omni problem, but it still charges...
What doesn't
SElinux is currently in permissive mode. Will not be going to enforcing, this would require a data wipe as well
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+
Everything else is not tested!!!
XDA:DevDB Information
Unofficial Omnirom 6.0 for Galaxy S 4G, ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99
Source Code: https://github.com/omnirom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: OmniRom
Version Information
Status: Beta
Created 2016-01-11
Last Updated 2016-05-12
Thanks Time!
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to the OMAP4 AOSP team for their work on porting CMA to a 3.0 kernel.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-6.0 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree (create the local_manifests folder if necessary).
After syncing the source, open a terminal and in the directory where you downloaded the source code type "./device/samsung/aries-common/patches/apply_patches.sh" to apply the patches necessary to have a working build. Then run "source ./build/envsetup.sh" and then "brunch galaxys4gmtd". For future builds, only the envsetup and the brunch parts are necessary. Please note that you will have to re-run the apply_patches.sh script after each time that you run repo sync. (Note: the patch script no longer runs automatically)
You should be able to use my trees for other first-gen galaxy S devices. You will need to apply a patch similar to https://github.com/xc-racer99/andro...mmit/fe6bc6b82881a12fc4a5647812f3cf0f52f79c6a to your device tree (if coming from Omni 5.1). I haven't done anything to P1 trees and may have broken the kernel for it...
Changelog
2015-12-20
Initial pre-release - many bugs
2015-12-26
Second pre-release - fewer bugs, but still plenty
2016-01-07
Initial actual release. Quite stable with minimal bugs
2016-01-23
Updated Omni Source code
Fixed Google Play (and other apps) download error (I think...)
New bootanimation - Its the new Omni one - it doesn't fit on our screen the best but it doesn't have one section lit up all the time so the screen doesn't burn in like the old one
Freed a bit more RAM
Improved zRAM performance by using LZ4 instead of LZO
Added T959P build
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
Added download mirror thanks to @FBis251
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Changelog for 2016-02-29
Updated Omni source - plenty of new features
Low-resource spinner from LegacyXperia (means that the loading spinner isn't the only thing using the CPU)
Miscellaneous performance tweaks (see github if interested)
md5sum for T959V: a7aa8cca3259208eafba7c2cccecdbfd
md5sum for T959P: 879256c93a0e58de0fb9c9e1be91e0e9
Changelog for 2016-04-02
Security fixes in the kernel
Freed roughly ~4MB of RAM in kernel
Updated android drivers resulting in better multitasking
OpenDelta updating system removed as we weren't using it (it used ~3MB of RAM)
Recents menu now has less lag when opened
Selinux contexts have changed. It could likely be put to enforcing now but this would require a complete data wipe so its still permissive
Live Wallpapers removed - we're low-ram
Bootanimation now fits the screen better
PowerHAL removed - it was broken and has been for a while...
Misc other changes - if you didn't notice problems, you won't notice the solutions
Known bug - Camera on T959V is broken...
md5sum for T959V: 247a721f4c27c5191a2a460e4c72ba3b
md5sum for T959P: d15339d8aa10f765155bdd8d1bb0c5f5
Changelog for 2016-04-08
Fixed camera on T959V
Security patch level of April 2, 2016 (latest to date)
Headset buttons fixed
T959V md5sum: 2b1560b99402c73275d1f69b3ceb9a22
T959P md5sum: e102cce0d624383fb85a32321c98c645
Changelog for 2016-05-09
Uses CMA kernel by default
Performance Control can now modify voltages
Systemless SuperSU is now supported
WebM playback is now working
EFS backup in TWRP now works
Data on boot should now work - no need to toggle airplane mode anymore
md5sum for T959P - 118789dd68760d9fd18cc961398bf346
md5sum for T959V - f9375a8d9792c3a0d222c113213c014d
Changelog for 2016-06-07
Security patch level of June 1, 2016
Microphone mute now works when in call
Battery now charges to 100% and should read properly after a system crash
Standby times should be improved
Slightly less RAM - but should result in better graphics performance
CMA crashes fixed (at least, I haven't crashed once since I started testing the patch a week or so ago)
PowerHAL is back - CPU is boosted when turning screen on to avoid delay
md5sum for the T959P: eeed77fb84189e84f2264e32d18ce454
md5sum for the T959V: b6457319d248029429183c342514b072
Changelog for 2016-08-02
First unified build (ie it works on both the T959P and T959V)
Screen recording now works in portrait mode
MMS should be able to be sent when data is disabled (will still use data though)
Default Camera app portrait photos are no longer square
SuperSU systemless updated to 2.76
Slightly less audio latency with UI sounds (and some sounds have changed)
Data should also be working on boot
Slight changes to battery and graphics config
Security patch level of August 5, 2016 (I'm a time traveller...)
md5sum: df587e0bd69552e0ece4b4ba3e214f45
Source, Downloads, Misc Notes
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see android-6.0-t959v branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-6.0 branch). The patches folder holds all the necessary patches along with a script to apply the patches.
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-6.0 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-6.0 branch)
Downloads!
All builds are found at https://drive.google.com/folderview?id=0B7vXjzo0Hj-iOGJ4dmdCd09OZmM&usp=sharing. As well, recent builds are mirrored on https://files.fernandob.com/#xc-racer99/Omni6.0
Gapps
Gapps cause the first boot to be very, very laggy. Things do improve after that. The best way to get through the Setup Wizard (IMO) is to skip everything possible (ie connecting to Wifi, settings up a Google Account, etc) and then reboot. You can manually add a Google Account later in Settings. While any (small) Marshmallow gapps should work, I have had success with OpenGapps pico package from www.opengapps.org (untested on recent builds).
SuperSu
SuperSu can be found at http://forum.xda-developers.com/apps/supersu. If on May 2016+ builds, systemless 2.71 works (other systemless versions may work, untested). If you're on an older build, you need to either force system mode (create a file in /system or /data called .supersu with the contents "SYSTEMLESS=false") or use an older version (ie version 2.52 or earlier). August 2016 build updates the systemless to 2.76.
Woooow thanks
As you suggested, Gapps caused lots of problems...made the ROM very slow and laggy, lots of FC's, lots of random reboots, etc. I re-flashed without Gapps. Was able to restore apps with TB and root with SuperSu. The basics...calling, browsing, messaging, camera...are working fine. Haven't taken it for a ride yet, but GPS test picked up 5 satellites and I haven't even taken it outside yet. If I desperately need another app, I guess I can find the .apk somewhere. Since I did a TWRP backup, maybe next week I'll try the pico gapps again and see what happens. At any rate, wonderful work.
Update: Took it out for a spin this afternoon....GPS works fine.
Been running the 1/7 for a few days. loving it so far
New Build Uploaded!
Alright, I've uploaded a new build
Changelog for 2016-01-23
Updated Omni Source code
Fixed Google Play (and other apps) download error (I think...)
New bootanimation - Its the new Omni one - it doesn't fit on our screen the best but it doesn't have one section lit up all the time so the screen doesn't burn in like the old one
Freed a bit more RAM
Improved zRAM performance by using LZ4 instead of LZO
I've also uploaded a T959P build as I had a request for one. Let me know if you guys find any more bugs.
New build flashed fine although I had to re-flash the SuperSU zip...no problem since I already had it on my SD card. I'll let it rest up for a day or two and then I'll try to flash the pico-gapps and see if it
will run smoothly....good job.
DickyG said:
New build flashed fine although I had to re-flash the SuperSU zip...no problem since I already had it on my SD card. I'll let it rest up for a day or two and then I'll try to flash the pico-gapps and see if it
will run smoothly....good job.
Click to expand...
Click to collapse
Sounds good. Do note that when/if you flash gapps, you will need to do a complete data wipe first, otherwise you will get force-closes like crazy.
I've always just reflashed SuperSU manually and never relied on the script to restore it so I can't help you there.
Tried to install over MTD SlimSaber with TWRP 2.7.0.0, kept getting Status: 7 error with updater.sh script.
Any way to fix this?
Thanks in advance.
SuccubusInc said:
Tried to install over MTD SlimSaber with TWRP 2.7.0.0, kept getting Status: 7 error with updater.sh script.
Any way to fix this?
Thanks in advance.
Click to expand...
Click to collapse
Hmm, going back to to stock with a OneClick/Heimdall/Odin will work for sure.
Alternatively, check if there is an omni.cfg file on your SD card. If there is, delete it and try again. Also, if you can get me the exact wording of the error output that would be great, along with the omni_mtd.log file from the SDcard.
xc-racer99 said:
Hmm, going back to to stock with a OneClick/Heimdall/Odin will work for sure.
Alternatively, check if there is an omni.cfg file on your SD card. If there is, delete it and try again. Also, if you can get me the exact wording of the error output that would be great, along with the omni_mtd.log file from the SDcard.
Click to expand...
Click to collapse
I will Heimdall One-Click back to KJ6 and reflash the ROM after checking for the omni.cfg, and will quote the output and the log if I get another error.
I'll be back by 5:00pm PST. I have school to take care of.
UPDATE:
Tried again after a full wipe [not a restore to stock] and got this:
Installing '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: run_program("/tmp/updater.sh") = = 0
E:Error executing updater binary in zip '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'
Error flashing zip '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'
Updating partition details...
Click to expand...
Click to collapse
Is there any kernel/recovery you recommend for flashing after restoring to stock?
I've tried before on AntonX Voodoo Lagfix recovery and got a similar error.
SuccubusInc said:
I will Heimdall One-Click back to KJ6 and reflash the ROM after checking for the omni.cfg, and will quote the output and the log if I get another error.
I'll be back by 5:00pm PST. I have school to take care of.
UPDATE:
Tried again after a full wipe [not a restore to stock] and got this:
Is there any kernel/recovery you recommend for flashing after restoring to stock?
I've tried before on AntonX Voodoo Lagfix recovery and got a similar error.
Click to expand...
Click to collapse
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
xc-racer99 said:
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
Click to expand...
Click to collapse
I'll try out Blastoff if I can find it. But it probably failed because I did not partition my sdcard. I'll see if that helps later.
Thanks a lot.
xc-racer99 said:
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
Click to expand...
Click to collapse
Hey, xc-racer99, after about four assorted blind attempts at installing your work, I flashed back to stock/AntonX kernel with Heimdall and full wiped, then used CWM to create a 4GB partition on my sdcard. The ROM installed through CWM, then TWRP without an error and booted up after fifteen minutes or so of OMNI animation, and is running on my SGS4G without any issues. The only noticeable lag was for the first five minutes after the initial boot. Now my device is gliding smoothly after a few tweaks in the performance settings and turning off background processes. Thank you so very much.
Next time, I'll read the entire post before blundering through the install process with the assumption that I know what I'm doing [as usual].
Sorry for the trouble, if indeed I was any.
xc-racer99 said:
Alright, I've uploaded a new build
Changelog for 2016-01-23
...
Fixed Google Play (and other apps) download error (I think...)
...
Click to expand...
Click to collapse
I tried Pico gapps and the store works perfectly for me now. Thanks!
New Build Uploaded!
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Still the same bugs present - headset buttons broken (have been on all 3.0 kernel-based ROMs for the Galaxy S 4G), laggy 720p recording, broken webM playback, microphone mute in calls, and bluetooth tethering.
Download link is the same as it always is. Also, thanks to @FBis251, we now have a mirror. It is located at https://files.fernandob.com/#xc-racer99//Omni6.0
Wooow...thanks
xc-racer99 said:
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Still the same bugs present - headset buttons broken (have been on all 3.0 kernel-based ROMs for the Galaxy S 4G), laggy 720p recording, broken webM playback, microphone mute in calls, and bluetooth tethering.
Download link is the same as it always is. Also, thanks to @FBis251, we now have a mirror. It is located at https://files.fernandob.com/#xc-racer99//Omni6.0
Click to expand...
Click to collapse
Finally got pico gapps to run...the initial setup took quite a while but now that it's settled in, no problems. It's also interesting to note that Link2SD is running fine while it seems to be a major problem for other Lollipop & Marshmallow ROM's on other devices.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
Click to expand...
Click to collapse
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 below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Downloads
Latest builds: https://www.mediafire.com/folder/cwzwh1c90stij/SM-G355HN
Google Apps: http://wiki.cyanogenmod.org/w/Gapps
Installation
1. TWRP Recovery required:
http://forum.xda-developers.com/galaxy-core/development/samsung-galaxy-core-2-sm-g355h-m-t2998094
2. Copy ROM on your ExtSdCard
3. Reboot into Recovery using 3-button-combo (home + volume up + power)
4. Do a Nandroid backup!!!
5. WIPE (wipe data/factory reset/wipe cache partition/internal storage)
6. Install the ROM from extarnal SD card using TWRP Recovery
7. Install Root from here:
http://forum.xda-developers.com/galaxy-core/help/root-galaxy-core-2-t2966445
8. Optionally install the Google Addon
Known Issues
Please do not report bugs if it is already listen in the list of known issues
* Some CyanogenMod features a missing - please do not file bug reports for those.
* Cannot set value via custom brightness "Edit" menu
* No account selected for Backup (gapps problem?)
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
* Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
* If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
* If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved
Known issues of current build :
* GPS not working. Will be soon.
* root doesn't work trough developers options
* What you report.
This ROM wouldn't be possible without:
* CyanogenMod
* Samsung Open Source Center
@ngoquang2708
@doesntexits
@cleverior.ipul
Sorry if I forgot someone
XDA:DevDB Information
kanas3gnfcxx (SM-G355HN), ROM for the Samsung Galaxy Core
Contributors
Y300-0100
Source Code: https://github.com/Y300-0100?tab=repositories
ROM OS Version: 4.4.x KitKat
Version Information
Status: Alpha
Created 2016-04-13
Last Updated 2016-04-13
changelog
20160415
* Fixed low volume while using headphones and playing music
2016 04 23
* Fixed NFC (not all tags can be detected )
2016 04 27
* Fixed freeze phone when try to turn of developer options, add Torch thanks to @doesntexits
And when you recording videos first change setting's of audio codes in camera settings.
@Y300-0100
Great work
I got one Q: Did this phone support dual-SIM? I see only one signal there
Also, the correct device codename is kanas3gnfc, not the xx suffix. You can get the right codename in the rootdir folder
How to install in SM-G355M?
Amazing work, i have a noob question, how can i install in SM-G355M?
Thank u , n sorry for my bad english
doesntexits said:
@Y300-0100
Great work
I got one Q: Did this phone support dual-SIM? I see only one signal there
Also, the correct device codename is kanas3gnfc, not the xx suffix. You can get the right codename in the rootdir folder
Click to expand...
Click to collapse
No. HN is single sim model only and code name is kanas3gnfcxx from stock build prop and https://androiddevice.info/submission/29929/show
I realize that when I get asserts prop error with kanas3gnfc when I tried to install rom.
Marco123V said:
Amazing work, i have a noob question, how can i install in SM-G355M?
Thank u , n sorry for my bad english
Click to expand...
Click to collapse
later today when I upload it...
for testing because i don't have M
Y300-0100 said:
No. HN is single sim model only and code name is kanas3gnfcxx from stock build prop and https://androiddevice.info/submission/29929/show
I realize that when I get asserts prop error with kanas3gnfc when I tried to install rom.
Click to expand...
Click to collapse
That's the recovery's fault, since it only get the .name instead of .device
If you say so, the codename in cm is cm_kanas3gnfc than the xx suffix (just like the .name in stock). Also, you can add kanas3gnfcxx in TARGET_OTA_ASSERT_DEVICE flag, so no installation error is produced
Y300-0100 said:
7. Install Root from here:
Click to expand...
Click to collapse
No need for this, since userdebug builds already rooted
Vv
What about the SM-G355H ? will it work or no ?
update-script not working for variant M
Detele is assert for working
Not Working:
-MTP
-Disable Developer Option or Debugging caused bootlop
Joaquin Scala said:
update-script not working for variant M
Detele is assert for working
Not Working:
-MTP
-Disable Developer Option or Debugging caused bootlop
Click to expand...
Click to collapse
1. you are using twrp for kanas3gnfc
2. to fix mtp I need stock boot.img for H and M because of ramdisk files
3. that I don't know. Don't have that issue. if phone reboots when you disable or enable Developer Option or Debugging use grab /proc/last_kmsg
as I mentioned in first post.
4. currently I trying to fix low volume issue!!
5. As you all know I own only SM-G355HN and as I mentioned before there has to be maintainer for each device.
6. What I did regarding twrp for H and M, fix wifi and build roms for them it's because I wanted to encourage other devs (or user enthusiasts )who own devices to include themselves to build. Because I can see here on xda some folks started with development from scratch
7. end
and PS.
All my sources are up to date so anyone can use them and with detailed instruction how to build
https://github.com/Y300-0100/android_device_samsung_kanas3g
https://github.com/Y300-0100/android_device_samsung_kanas3gub
https://github.com/Y300-0100/android_device_samsung_kanas3gnfcxx/blob/master/README.md
fixed low volume issue!!
YES
I fixes low volume during typing stupid post above in 5 min.
So if you want me to commit it to my github I want to see 1000 thanks click by tonight
PS.
No 1000 more like 10 000
Y300-0100 said:
YES
I fixes low volume during typing stupid post above in 5 min.
So if you want me to commit it to my github I want to see 1000 thanks click by tonight
PS.
No 1000 more like 10 000
Click to expand...
Click to collapse
Well, if mods see this, your account will be... you know
Btw, good job. It's good to see more SPRD devices get CM
doesntexits said:
Well, if mods see this, your account will be... you know
Btw, good job. It's good to see more SPRD devices get CM
Click to expand...
Click to collapse
Thanks for info. But I didn't use any offensive word and if you are referring to 10 000 it's joke ended with
If they think that something should be "done" with my account so be it.
BTW it's already up to date. You know what
Y300-0100 said:
Thanks for info. But I didn't use any offensive word and if you are referring to 10 000 it's joke ended with
If they think that something should be "done" with my account so be it.
BTW it's already up to date. You know what
Click to expand...
Click to collapse
OK, the "10000" is what i referenced
Btw, seems you're missing some libs to get NFC working. Did you tried with any tags/devices?
If it doesn't work then, take a look at this: https://github.com/TheNikiz/android...fc3g/blob/cm-11.0/device_vivaltonfc3g.mk#L101
Some extras configs/packages for NFC are included there. See if any of them works with you
asser19 said:
What about the SM-G355H ? will it work or no ?
Click to expand...
Click to collapse
Sound fix will be but as I mentioned before MTP wont be fixed unless someone provide me stock boot.img for SM-G355H and SM-G355M.
and for a notice I have slow PC so for each build I need aprox 8 hours.
Build for SM-G355HN is uploading right now in SM-G355HN folder on mediafire.
doesntexits said:
OK, the "10000" is what i referenced
Btw, seems you're missing some libs to get NFC working. Did you tried with any tags/devices?
If it doesn't work then, take a look at this: https://github.com/TheNikiz/android...fc3g/blob/cm-11.0/device_vivaltonfc3g.mk#L101
Some extras configs/packages for NFC are included there. See if any of them works with you
Click to expand...
Click to collapse
I'm lazy. I will add packages and files for NFC. I did it before for some other devices, will tray to add FM and screen recording if hardware support it.
Y300-0100 said:
I'm lazy. I will add packages and files for NFC. I did it before for some other devices, will tray to add FM and screen recording if hardware support it.
Click to expand...
Click to collapse
FM is not supported by CM, so you've to implement your own
Also screen recording too. But, screen recording will lag like sh*t on these such devices
Y300-0100 said:
Sound fix will be but as I mentioned before MTP wont be fixed unless someone provide me stock boot.img for SM-G355H and SM-G355M.
and for a notice I have slow PC so for each build I need aprox 8 hours.
Build for SM-G355HN is uploading right now in SM-G355HN folder on mediafire.
Click to expand...
Click to collapse
Here is the stock boot.img form SM-G355M, it's from the last Samsung Update
boot.img
Hello, you can install the rom with TWRP-3.0.2-0-kanas3gnfc.img normally. Now I work MTP. Thank you very much, hoping for a newer version of android L or M.