Database Info

[ROM][UNOFFICIAL][DEV] [WIP] CM 11.0 for Galaxy Grand Neo (I9060) [ALPHA]

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.
Code:
#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.
*/
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.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Device-specific source code for the Samsung Galaxy Grand Neo Duos are available from https://github.com/SamsungBCM-Grandneo
(For developers only - the patches are already included in the ROM)
Patch to system/core for RIL to work: https://gist.github.com/pawitp/5372673.
Patch to hardware/broadcom/libbt for bluetooth to work: https://gist.github.com/pawitp/7891380.
Patch to frameworks/native to support legacy binaries: https://gist.github.com/pawitp/7891421
Patch to frameworks/native to workaround hwc issues: http://review.cyanogenmod.org/53162/ and https://gist.github.com/pawitp/7891444.
Patch to frameworks/av to fix audio/video issues: https://gist.github.com/pawitp/7945188
Patch to external/chromium_org to workaround hwc issues: https://gist.github.com/pawitp/7910708
Patch to packages/app/SamsungServiceMode to fix service mode: http://review.cyanogenmod.org/57400/
Dual SIM Patches: https://gist.github.com/pawitp/9433442
Patch to frameworks/opt/telephony to fix non-looping ringtone issue: https://gist.github.com/pawitp/0f400e7b5cfb9bc70c25
Do not submit bug on CyanogenMod issue tracker
Downloads
ROM: https://s.basketbuild.com/devs/LuK1337/_grandneo/
Google Apps: http://wiki.cyanogenmod.org/w/Gapps
Note: The ROM download page also provide a CWM-based recovery image compatible with CM 11 flashable with Odin.
What works?
Wi-Fi
Bluetooth
RIL ( SMS, Mobile Data)
Dual SIM (Experimental - SEE FAQ)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Camera (photo & video)
Video playback
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues
incall audio not working ( mic and speaker)
screenrecord does not work
FM Radio does not work (you can use SpiritFM, but I'm not providing support for any problem)
Stock browser does not use hardware acceleration (Please use Google Chrome)
Sometimes wake up causes music stutter
Cannot changed advanced settings from dialer settings (e.g. reverse lookup) when dual SIM is enabled
Compass in "Sygic" app (works fine in other apps)
Does not work on 4.1 stock ROM's bootloader, please upgrade to 4.2 before flashing
Additionally, Dual SIM has the following limitations:
Both SIMs are always enabled (no way to disable one SIM)
"Receive incoming call while data is enabled" is always enabled
The QuickSettings tile will display the status for the currently selected SIM for data
There is no arrow activity indicator in the status bar.
Changing 2G/3G network mode using the QuickSettings toggle is not supported, only do it from Settings.
3G may not work properly if Dual SIM mode is enabled with only 1 SIM inserted
Cannot set different ringtone for each SIM
Call logs doesn't know the incoming SIM
Installation
Make a backup!
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to 4.2.
Install TWRP recovery with SELinux support. Older CWM will result in a "status 7" error.
Install the ROM using TWRP
Optionally install the Google Apps Addon
Wipe data if coming from stock
Optionally enable dual SIM support (See FAQ)
To upgrade to a newer build, simply flash the zip. There's no need for data wipe or flashing Google Apps again.
Changelog
20141002: Initial release
FAQ
How do I enable/disable Dual SIM?
Dual SIM support is enabled by default. If you only use 1 SIM and wants to disable Dual SIM support, you can use the following instruction:
Enable:
Code:
su
setprop persist.radio.multisim.config dsds
Disable:
Code:
su
setprop persist.radio.multisim.config none
(Instruction screenshots)
Can you include Feature X into your ROM?
No. This ROM will have CyanogenMod's feature set.
Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
No. This is an AOSP ROM and cannot have TouchWiz applications.
Can you include call recording?
No. CyanogenMod does not include call recording to avoid potential legal issues.
Can you add Feature X to the stock ROM?
No. I don't work on stock ROMs.
What kernel does this ROM use?
A slightly modified version of the stock kernel, the source code is linked above.
I've heard that Broadcom doesn't release source, how can you make this ROM?
Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Can I use your ROM as a base?
http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Will you make this official CM?
Due to the amount of work and commitment involved, I am not planning to make an official CM port.
Can contacts be saved to phone/SIM?
No. It is not supported in AOSP-based ROMs.
Can I send files over Wi-Fi Direct?
Yes, but you must use third-party applications. The implementation provided on Samsung ROMs is not an open standard. AOSP/CM does not provide a native way to send files over Wi-Fi Direct.
Can I mirror your ROM?
You're free to, but I will not list it in this post.
Will feature X from a previous version of CM be implemented?
I don't know, probably will be, eventually. I don't really involve myself in the feature-set side of CM.
Will you OTA support?
No. CM Updater is present on the device, but it only works for official devices. I'm not interested in adding an alternative update mechanism. If you want to know when a new ROM is released, follow the rss feed at http://goo.im/rss&path=/devs/pawitp/i9082_cm11.0.
I cannot add APNs
Make sure you set the correct MCC/MNC code, the APN will not appear otherwise. Also make sure to use menu -> save (back button means discard).
Recovery asked me "ROM may flash stock recovery on boot. Fix?"
Short answer: "yes" or "no" doesn't matter
Long answer: Newer versions of CM starts including recovery with the ROM. However, this does not get flashed unless the "Update CM recovery" option in system settings gets ticked. If you say "no", the current recovery will not get overwritten (unless you enabled the "Update CM recovery" option), but it will continue prompting you every time. If you say "yes", CM's recovery flashing mechanism will be disabled until a newer version of the ROM is flashed.
I get "Throttle Limited Exceeded" or "We currently accept only US numbers" when an unknown number calls
It's a bug of all CM11 ROMs with the reverse lookup code in the dialer. You can work around it by
1) Disable dual SIM
2) Go to dialer settings and disable "reverse lookup"
3) Re-enable dual SIM
Does this custom kernel work? Does this app work on this ROM?
Please ask the in Q&A thread maintained by chotu22. If you're experiencing any problems while running a custom kernel or other system modifications, please remove those modifications and test again before filing a bug report.
Reporting Bugs
You are allowed to report bugs only in this thread.
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. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your--
Phone model (I9060 or 9060L):
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
Dual SIM:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- My real-life friend for letting me borrow his phone to work on this
- RampantRhino for donating a phone to help me continue with this project
XDA:DevDB Information
[ROM][UNOFFICIAL] CM 11.0 for Galaxy Grand Neo (I9060) , ROM for all devices (see above for details)
Contributors
rutvikrvr, luk1337, baran0119
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2014-10-02
Last Updated 2014-10-24

thx....love to try cm on my friends phone..,..

thanks!! but can you finish this rom pls? i would enjoy it if you fix that incoming calls mic audio issue. pls

superlouro said:
thanks!! but can you finish this rom pls? i would enjoy it if you fix that incoming calls mic audio issue. pls
Click to expand...
Click to collapse
After the 13 th... I Have exams till then

thank you so much. i'll be w8ing for you. i would love so much to use it omg

i put the cm-11-20140920-UNOFFICIAL-baffinlite.zip file on the sd and i tried to flash it using the TWRP-2.8.0.1_RECOVERY-baffinlite-20141008.tar.md5 but i'm still getting an error. it just says Failed. I tried flashing from the internal storage and from the SD but nothing, just an error
"Error executing updater binary in zip ' /sdcard/cm-11 (..).zip " FAILED

any news?
waiting incall audio works fine

@rutvikrvr
Hi, please scroll down the page and add to tags "gt-i9060"
It will be nice to see more threads under
http://forum.xda-developers.com/tags.php?tag=gt-i9060
because we have not own subforum
thanks in advance

any progress?

any news devs?

superlouro said:
any news devs?
Click to expand...
Click to collapse
Sadly we haven't had the time to look into it... But we will ressurect this project soon.... No eta pl

thank you!!

Feedback issues
For the last night, I tried to replace for recovery with TWRP instead of unofficial PhilZ CWM after successfully flashed since last month ago, then I wiped all of the data away from the stock ROM except for external storage, and then I installed an unofficial CM 11 ROM.
EDIT I: Never mind, the previous build (9/17/2014) still works, but it has a red exclamation mark is in again, and not current (9/20/2014).
EDIT II: My father told me for invoice calling seems doesn't work unless you have solved to fix the problem.

any news devs?

superlouro said:
any news devs?
Click to expand...
Click to collapse
sorry college is a time for learning, and I have an exam every week
maybe someone else will do it ...

I have not tested it yet, but is incall mic and speaker working if i use only 1 SIM, instead of 2?? Tell me YES ahahaha

superlouro said:
I have not tested it yet, but is incall mic and speaker working if i use only 1 SIM, instead of 2?? Tell me YES ahahaha
Click to expand...
Click to collapse
Nop.. We tried everything.. Like connecting to Bluetooth headset and even speakers through AUX but seriously.. Nothing works..!

what about call reception? if some calls me, can i ear and speak with him? or this issue is affecting calling and call reception?

superlouro said:
what about call reception? if some calls me, can i ear and speak with him? or this issue is affecting calling and call reception?
Click to expand...
Click to collapse
You can receive the call(if on single sim version single sim has network issue) but no voice exchange..! Like the opposite person also can't here you..!

that's the problem of dual SIMs.. but Grand Duos i9082 is working well

[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project

[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.

[ROM][CM11][SM-G355HN][CyanogenMod 11.0][UNOFFICIAL]

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.

[ROM][8.1.0][UNOFFICIAL][GO] LineageOS 15.1 || Alpha 2 || 10 June 2018

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.*/
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
All of the LineageOS source code is available on their github.
What's NOT working
Camera
Hotspot
Installation instructions
Boot to recovery mode, use TWRP 3.0.2 only as TWRP 3.0.0 reportedly has issues with flashing it.
Do a factory reset.
Flash ROM, then flash GApps, and then flash the addons if any.
Reboot. First boot will take time.
Downloads
ROM - AndroidfileHost
Source
Device Tree
Kernel Source
Credits
@Olivier @AdrianDC
@Agent_fabulous @STRYDER~007
@AdrianDC and all others who worked in development for Sony devices.
XDA:DevDB Information
LineageOS 15.1, ROM for the Sony Xperia L
Contributors
corphish
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Version Information
Status: Alpha
Created 2018-02-19
Last Updated 2018-06-10

F.A.Q
Q. Why pre-alpha and all?
The reason why this build is pre-alpha, and in other words, simply unusable, is because deep sleep doesn't work, that means the phone cannot be kept idle (it can be if connected to power source). This is a big issue as it renders other (basic) functionalities useless. I wanted to fix this and then release, but have been out of luck. So I decided to release this anyway, just to let people know that work is being done on getting Lineage 15.x work on Xperia L. Even if this fails big time and the project needs to be abandoned, well atleast the people would get to use whatever worked. Ofcourse I am not giving up yet, unless I really really get frustrated. As of this build, flash it if interested, see how oreo looks like, and then flash back the old rom.
Q. What GApps to flash?
I did not use GApps during my testing, but if you want to use, use opengapps (8.0 ARM). Recommended - pico or micro packages. You do need to modify the installer scripts inside opengapps zip, otherwise installation would fail due to version mismatch.

Changelog
20180610 (Alpha 2)
- Fixed mobile data.
- Fixed issue which caused downloads to fail.
- Updated lineage sources.​
20180224 (Alpha 1)
- Fixed deep sleep.
- Fixed proximity sensor.
- Updated lineage sources.​
20180219 (Pre-alpha)
- Initial release.​

Wow,I was excited,until the moment when my phone turned off and on,every 2 minutes,data transmission not working,I count on amendments in future updates.

Thanks dev.
#Taoshan4ever.

thank you bro. been waiting for this for a long time, many cheers to you

Deep sleep issue was present in every LOS 15 rom, especially lenovo roms, Can it be fixed by replacing libsuspend.so from nougat rom, what's actually the issue

kish11 said:
Deep sleep issue was present in every LOS 15 rom, especially lenovo roms, Can it be fixed by replacing libsuspend.so from nougat rom, what's actually the issue
Click to expand...
Click to collapse
In oreo, earlysuspend got removed from libsuspend, and our kernel uses used earlysuspend. So during initial boot (that is our kernel using earlysuspend, and no earlysuspend in libsuspend), device won't comeback on after I turn off the display, even if it was connected to power source.
An abandoned patch does exist though, which brings back earlysuspend support back to libsuspend. With that patch applied, device did comeback on after display was turned off, and it would function normally as long as power supply was connected to it (just like how it does now), deep sleep still did not work then.
Since the patch was abandoned, and depending on it would not be appropriate, I decided to bring autosleep in kernel, which I eventually did, deep sleep still doesn't work

Great!
Thanks for your hard working and not giving up :good:
It's worth testing, at least we can see how it looks like

wow this is a good news, but i think with more 800MB ram taoshan should use android go

Thank you for your hard works:angel: Corphish :angel:
Hope the bug dies soon :laugh:

Alpha 1
New build is up.
Changelog
Fixed deep sleep.
Fixed proximity sensor, now all the sensors should be working as usual.
Updated lineage-15.1 sources - Switched from staging/lineage-15.1 branch to lineage-15.1 branch. Some immediate changes you will notice are the new icons and the addition of Lineage setup wizard.
Now that this has graduated from pre-alpha, and the device can stay awake in idle, this makes the alpha build way more usable than the pre-alpha build. If you end up using this, and face bugs that are not mentioned in the "not working" list, please let me know by posting about it in this thread. Logs would be welcome, but a proper way of reproducing it would be good too.
P.S - Firefox still doesn't work ¯\_(ツ)_/¯
Links updated in OP.

1. device not booting properly using restart in power options, doesn't respond to any action until battery removed
2 flashlight not working, and the flashlight toggle interrupts the music playback.
3 downloads fail using jelly browser
and, cheers for your hard work @corphish, Thank you

kish11 said:
1. device not booting properly using restart in power options, doesn't respond to any action until battery removed
2 flashlight not working, and the flashlight toggle interrupts the music playback.
3 downloads fail using jelly browser
and, cheers for your hard work @corphish, Thank you
Click to expand...
Click to collapse
1. It works fine here, does take a bit of time though. :/
2. Because camera does not work. It will work when camera is fixed.
3. That is because, vold assigns our internal storage name as "7384-14B3" (atleast it looks like that in mine), so storage location for internal storage is "/storage/7384-14B3". Turns out that DownloadManager cannot handle storage locations with such name . Will try to workaround it in the next build.

Now that's awesome and quick. Great work @corpish

I have tried it. It's amazing and fast
But there are some problems
1. Phone restarts when phone get stuck, or when starting camera
2. Music playback stopped when flash light turned on
3. Downloading get unsuccessful in the stock browser
I think other users have already mentioned some of the following problems.( I think the real problem is with the download manager )
4. And there was no gapps for Oreo 8.1.
So I installed a unofficial gapps which was created for 8.1 and the setup keeps closing
I have only noticed these problems yet.
But it's a amazing ROM.
Thanks Corphish

Nikhil kuttu said:
I have tried it. It's amazing and fast
But there are some problems
1. Phone restarts when phone get stuck, or when starting camera
2. Music playback stopped when flash light turned on
3. Downloading get unsuccessful in the stock browser
I think other users have already mentioned some of the following problems.
4. And there was no gapps for Oreo 8.1.
So I installed a unofficial gapps which was created for 8.1 and the setup keeps closing
I have only noticed these problems yet.
But it's a amazing ROM.
Thanks Corphish
Click to expand...
Click to collapse
I have the same problems

Split screen is not working.it says not supported in any app even sys app.
And casting is not working as well.just after connecting it closes and search for device again
These are not a major problems
But the camera and flash are little impotent

Nikhil kuttu said:
Split screen is not working.it says not supported in any app even sys app.
And casting is not working as well.just after connecting it closes and search for device again
These are not a major problems
But the camera and flash are little impotent
Click to expand...
Click to collapse
If camera and flash are important then,
Flash Back !

I wont change my OS just to get camera and flash
Working again.
Even while it's in alpha stage I really like this Rom:laugh:
The app's stay in the same position even after long time
And now I'm using mostly Google go edition app's to keep the device fast as possible

[ROM][XC][O][8.1][UNOFFICIAL]Paranoid Android 8.0.0-DEV

Obligatory disclaimer:
Code:
[SIZE="1"]/* 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.
*/[/SIZE]
Preface:
Thanks in no small part to the awesome help from Tim Graham of the AOSPA-team, I was able to compile an unofficial build of Paranoid Android 8.0.0-DEV (Android 8.1)
for the Sony Xperia X Compact (kugo/f5321). I've been using it for a couple of days now without running into any (rom-specific) issues yet.
I've asked Tim if he didn't mind me posting the rom here and he gave the go ahead. So here we go!
Installation instructions:
* Backup important files beforehand just in case something goes awry.
* Wipe System, Cache and Data.
* Install zip-file with TWRP.
* Unzip and then flash Sony's ODM-image (v15) to the oem-partition using fastboot:
Code:
fastboot flash oem SW_binaries_for_Xperia_Android_8.1.6.4_r1_v15_loire.img
What works:
* Data (2G/3G/4G/LTE)
* Wifi
* GPS
* Encryption
* Bluetooth
* Fingerprint sensor
* Camera
* Torch
* GApps (Open GApps 8.1 pico)
* Magisk (16.4)
Known issues:
* Boot animation is partly distorted (Needs to be addressed by Sony)
* Night Mode doesn't work (Needs to be addressed by Sony)
* The occasional battery drain (Same as with other custom oreo roms. Mine seem prevalent whenever cell reception is spotty)
If you come across any bugs, please feel free to report them here. I am not the developer, but our feedback might contribute to making a better eventual official version of this ROM.
Download:
https://androidfilehost.com/?w=files&flid=269311

harryharryharry said:
Obligatory disclaimer:
Code:
[SIZE="1"]/* 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.
*/[/SIZE]
Preface:
Thanks in no small part to the awesome help from Tim Graham of the AOSPA-team, I was able to compile an unofficial build of Paranoid Android 8.0.0-DEV (Android 8.1)
for the Sony Xperia X Compact (kugo/f5321). I've been using it for a couple of days now without running into any (rom-specific) issues yet.
I've asked Tim if he didn't mind me posting the rom here and he gave the go ahead. So here we go!
Installation instructions:
* Backup important files beforehand just in case something goes awry.
* Wipe System, Cache and Data.
* Install zip-file with TWRP.
* Unzip and then flash Sony's ODM-image (v11) to the oem-partition using fastboot:
Code:
fastboot flash oem SW_binaries_for_Xperia_Android_8.1.6.4_r1_v11_loire.img
What works:
* Data (2G/3G/4G/LTE)
* Wifi
* GPS
* Bluetooth
* Fingerprint sensor
* Camera
* Torch
* GApps (Open GApps 8.1 pico)
* Magisk (16.4)
Known issues:
* Boot animation is partly distorted (Needs to be addressed by Sony)
* Night Mode doesn't work (Needs to be addressed by Sony)
* The occasional battery drain (Same as with other custom oreo roms. Mine seems prevalent whenever cell reception is spotty)
If you come across any bugs, please feel free to report them here. I am not the developer, but our feedback might contribute to making a better eventual official version of this ROM.
Download:
https://androidfilehost.com/?w=files&flid=269311
Click to expand...
Click to collapse
Thanks for keeping XC alive. I haven't been too interested in Android since finding Sailfish, (especially since there's been so little activity here), but might bounce back to check this out.

Has anyone already testet whether Car Bluetooth is working? Does encryption work?
Thanks for any replies in advance.

Encryption works. I can't say for sure car bluetooth works. The bluetooth devices I use (heart rate monitor and earbuds) do work though.

harryharryharry said:
Encryption works. I can't say for sure car bluetooth works. The bluetooth devices I use (heart rate monitor and earbuds) do work though.[/QUOTE
very good!!
Click to expand...
Click to collapse

Thread cleaned.
:good:

When tried to flash with TWRP (wiped everything beforehand), got the following error:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard1/pa_kugo-8.0.0-
DEV-20180507.zip'
Anyone know why this is happening?

Looks like the error is caused by the installation script checking if the rom is suitable for your device and concluding it isn't. What device are you flashing the rom to ?

Is the ROM source private?

No, the source is publicly available on github: https://github.com/AOSPA/manifest
NB: If anyone else is having problems with this rom, your best bet is to try the official rom - which I just saw has been released the 22nd of august:
http://get.aospa.co/official/kugo
I haven't tested the rom myself, but I'm willing to say it's the better choice overall since it is built more recently and therefore probably has a more up to date security patch level and so on.

harryharryharry said:
Looks like the error is caused by the installation script checking if the rom is suitable for your device and concluding it isn't. What device are you flashing the rom to ?
Click to expand...
Click to collapse
X Compact. The device it was supposed to be flashed on.

Hmm, that's strange. I think if you want to try out Paranoid Android, you're better off trying the official rom (which has been released a couple of days ago). If the same error message appears, all I can think of is maybe TWRP somehow doesn't report the correct brand/model of the phone..

Official rom looks good too.

I can't open my camera app. I'm using the official rom. Someone has this problem too?

Yes also the case for me (the screen stays black until I close the camera app), this wasn't the case with my unofficial build of the rom (although I tested with a much older version of the oem partition - I think version 11).
I'm not on the rom anymore because it was generally laggy and no music app would play music. I didn't bother to investigate further because for me the music app is pretty much essential in daily use and just needs to work.
If you want this worked out, your best bet is to contact the developers of the rom at their google plus page:
https://plus.google.com/communities/112514149478109338346
and under 'bug reports' provide them with a log (for example with matlog) for them to dissect.

Hi,
I habe recently flashed the official OA1 ROM of Paranoid Android for my Xperia X Compact and after it finally worked and it had booted I noticed some difficulties with the Bluetooth. It stops submitting the sound to various Bluetooth devices (headphone, music box) where this never happened before. (Side note: the 7.1.3. Official PA ROM features no bluetooth at all, at least not on my device.) Sometimes even the Bluetooth deactivated itself fully. After turning it back on, it would pair again but mostly after a few seconds stop delivering the sound to the devices. Is there a way to fix it? I'd love to hear your ideas to it.
Best
Calumet27
---------- Post added at 01:39 PM ---------- Previous post was at 01:23 PM ----------
harryharryharry said:
Yes also the case for me (the screen stays black until I close the camera app), this wasn't the case with my unofficial build of the rom (although I tested with a much older version of the oem partition - I think version 11).
I'm not on the rom anymore because it was generally laggy and no music app would play music. I didn't bother to investigate further because for me the music app is pretty much essential in daily use and just needs to work.
If you want this worked out, your best bet is to contact the developers of the rom at their google plus page
Hi,
was it due to lack of integration with the SD card? Because with mine in the official OA1, I do not have problems with the music directly, it plays (not m4a though), and I CAN show the contents of the SD card but other apps than the file manager cannot access the SD card. It is possible for me to play individual Songs via VLC though. I'd be thankful for your ideas in this.
Best
Calumet27
Click to expand...
Click to collapse