{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PLEASE READ BEFORE FLASHING
Upon flashing this ROM, your phone warranty is now VOID. You also understand that, upon flashing this ROM, there is no guarantee that ALL APPS work as they would normally, as this is NOT an official ROM provided by Samsung or the CyanogenMod team. You may experience bugs, and you are encouraged to report them along with a logcat. The contributors and developers (myself included) will not be held responsible for any abnormality this ROM may cause, including but not limited to battery drain and lag.
This ROM is ONLY TESTED on Samsung Galaxy Ace Plus (GT-S7500), other variants have not been tested and will brick your phone.
Introduction
CyanogenMod (pronounced sigh-AN-oh-jen-mod), is a customized, aftermarket firmware distribution for several Android devices. Based on the Android Open Source Project, CyanogenMod is designed to increase performance and reliability over Android-based ROMs released by vendors and carriers such as Google, T-Mobile, HTC, etc. CyanogenMod also offers a variety of features & enhancements that are not currently found in these versions of Android.
Working Features
Samsung RIL
Audio Playback
WiFi
Bluetooth
Mobile Data
Kernel supports overclocking
GPS
Proximity Sensor, Accelerometer, other sensors
Mounting of external SD Cards
Live Wallpapers
Camera
Fast Charging
Not Working
NONE (see note regarding bug below)
WiFi MAC Addresses are the same for all devices using this ROM (not a major issue. You can still use WiFi without problems. alternatively, you can use the fix located in this post: http://forum.xda-developers.com/showpost.php?p=63095528&postcount=1331 (thanks to @kk9999gada), which allows you to use your original MAC address, which fixes the issue.)
Installation Instructions
Create a backup of your current WORKING ROM.
Copy the flashable ZIP to your SD Card.
Wipe your data/cache, including the Dalvik Cache.
Flash as you normally would.
Reboot.
The first boot will take a long time, it is normal. Succeeding boot times will be significantly faster.
Screenshots
Downloads
Build #6 - Download Here
Gapps - Go Here - use PICO MODULAR PACKAGE - PROPER DPI PLAY SERVICES
MD5: c9464e6fa56e1d0f078f4b3ad1aff7da
Older Releases
Build #3 - https://www.androidfilehost.com/?fid=95864024717073277
Gapps - http://forum.xda-developers.com/showthread.php?t=2397942 - use PICO MODULAR PACKAGE - PROPER DPI PLAY SERVICES
Build #2 - https://www.androidfilehost.com/?fid=95832962473396097
Gapps - http://forum.xda-developers.com/showthread.php?t=2397942 - use PICO MODULAR PACKAGE - PROPER DPI PLAY SERVICES
Camera Flash and Audio Playback Fix: http://forum.xda-developers.com/showpost.php?p=57197821&postcount=34
Build #1 - https://www.androidfilehost.com/?fid=95747613655049902
Gapps - http://forum.xda-developers.com/showthread.php?t=2397942 - use PICO MODULAR PACKAGE - PROPER DPI PLAY SERVICES
WiFi Fix - View attachment 3040541 (thanks, @kk9999gada) - NOT NEEDED for Build #2 and above
Changelog
February 1, 2015 - Build #6
Fixed FM Radio (fully working)
Updated CyanogenMod Sources
Fixed Virtual Sensors (no longer breaks Camera HAL, we now have all sensors working again)
TONS of Kernel tweaks (lesser kernel panics, much more stable compared to previous builds)
Webview Lag is FIXED
A LOT of bug fixes have been implemented
January 7, 2015 - Build #4 (private release)
Initial fixes for Webview
January 1, 2015 - Build #3
Added preliminary support for FM Radio (hardware utilized but audio is not yet available, will be fixed in the future)
Camera is working again (after an update to CyanogenMod 11 Milestone 12 broke it during the testing phase for Build #3)
Sources updated to CyanogenMod 11 Milestone 12
Updated stock apps
Kernel tweaks and modifications
Legacy sensors re-enabled (thanks for the report, @kk9999gada) -- UPDATE: These sensors are temporarily disabled, they break the camera HAL. Will be fixed in a future build instead. The phone will still work fine, these are just virtual sensors anyway and does NOT affect the total performance of the phone.
Audio works after flashing (low-power audio disabled for our device)
Improved responsiveness
Tons of bug fixes
December 2, 2014 - Build #2
Fix Camera/Camera HAL
Fix build error from Java (invalid Switch statement arguments) - https://github.com/SpeedGroup/android_frameworks_base/pull/1
Improved Kernel Responsiveness
Fixed WiFi
Retained KitKat OMX Libraries
Fix FLAC-type metadata
December 1, 2014 - Build #1
Initial Upload
XDA:DevDB Information
CyanogenMod 11.0 for GT-S7500, ROM for the Samsung Galaxy Ace Plus S7500
Contributors
Liam D., Giugiu19, smartandroidtech, kk9999gada
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2014-11-30
Last Updated 2014-11-29
Frequently Asked Questions
Q: I want to build a ROM for Galaxy Ace Plus. Where do I start?
A: I'm looking into providing a tutorial soon so that other users can also build ROMs for our phone.
Q: Lollipop. When?
A: When KitKat for our phone is stable, Lollipop would be considered. But now, nope.
Q: I found a fix for a bug. Where do I send it?
A: You can PM it to me, or post it in the thread. ALL FIXES ARE WELCOME.
Q: Your sources?
A: All my sources are on my GitHub profile. I make sure that all my GitHub uploads can be built successfully before I publish them in order to avoid a lot of build errors.
Q: I want a transparent status bar. How do I do that?
A: /system/build.prop should be ro.config.low_ram=false (unchanged), then open Settings > Performance (you will only see this after enabling Developer Options, which you could do by going to Settings > About Phone and tapping the Build Number 7 times) > then check Force High-End Graphics then reboot.
ThankGod..!!!
There is still a ray of hope for our phone.!!
Great work Dev.!!
Sent from my GT-S7500 using XDA Free mobile app
Recently I saw in the galaxy mini 2 section that the camcoder has been fixed in cm 10.1 by using a precompiled gallery2.apk with working camcorder...in addiction I saw a commit that can could be useful ( https://github.com/bleached/android...mmit/af94d358984527323c5dcd6f6e7ebff942c6a35c ) ....could be helpful for our ace plus cm11, even if is based on kitkat? I hope so ......good work developer, I appreciate so much your work, your efforts.....keep it up...thanks!!!
AndroidVin said:
Recently I saw in the galaxy mini 2 section that the camcoder has been fixed in cm 10.1 by using a precompiled gallery2.apk with working camcorder...in addiction I saw a commit that can could be useful ( https://github.com/bleached/android...mmit/af94d358984527323c5dcd6f6e7ebff942c6a35c ) ....could be helpful for our ace plus cm11, even if is based on kitkat? I hope so ......good work developer, I appreciate so much your work, your efforts.....keep it up...thanks!!!
Click to expand...
Click to collapse
That's a good find. Will add that fix to the next build.
Liam D,
Great to see CM11 for our ace plus alive again here :good:, now what i really hope is camera & camcoder can fix on build 2 or next build update on future. especially the bugs of camconder are all the time of ace plus problem seems in JB till KK. appreciate for you hardwork honestly. hope can see the build 2 soon. the best is see ace plus still alive. :fingers-crossed:
bbivan said:
Liam D,
Great to see CM11 for our ace plus alive again here :good:, now what i really hope is camera & camcoder can fix on build 2 or next build update on future. especially the bugs of camconder are all the time of ace plus problem seems in JB till KK. appreciate for you hardwork honestly. hope can see the build 2 soon. the best is see ace plus still alive. :fingers-crossed:
Click to expand...
Click to collapse
I'm aiming for the camera fix. Right now the camera is being detected in the kernel, but could not load it because it seems to not read the Camera HAL module. The next build will be using a different version of the android frameworks that would allow the loading of the camera HAL. Right now the only problems we have in my logcats are the proprietary parts that Samsung did not make fully open-source.
For instance, our camera is a proprietary version of msm7x27a and even though there are other similar cameras on the similar boards, ours contain some lines of code from Samsung that we cannot reverse engineer, making it hard to re-create the camera module.
thanks
Dear developer liam
Thanks a billion times for trying cyanogen 11 on ace plus .
we appreciate your efforts.
Waiting for cm 11 bugfree
I'll be the first tester...
:fingers-crossed:
Liam D. said:
I'm aiming for the camera fix. Right now the camera is being detected in the kernel, but could not load it because it seems to not read the Camera HAL module. The next build will be using a different version of the android frameworks that would allow the loading of the camera HAL. Right now the only problems we have in my logcats are the proprietary parts that Samsung did not make fully open-source.
For instance, our camera is a proprietary version of msm7x27a and even though there are other similar cameras on the similar boards, ours contain some lines of code from Samsung that we cannot reverse engineer, making it hard to re-create the camera module.
Click to expand...
Click to collapse
ok i understand, i know is not the easy task especially what you are facing now for the camera issue, i see what i can help. Thanks. good luck & appreciated all the time.
I am VERY PLEASED to announce:
That I have fixed the Camera issue on Build #2. Camera is NOW WORKING!
New build will be uploaded later within the week after I have completed my testing.
Liam D. said:
I am VERY PLEASED to announce:
That I have fixed the Came
ra issue on Build #2. Camera is NOW WORKING!
New build will be uploaded later within the week after I have completed my testing.
Click to expand...
Click to collapse
Wow....really good news! You are great:thumbup: how is camcorder? Work as well anyway thanks for you hardwork... Cannot wait for download build 2 .... Thanks & congratulation. :thumbup:
Updated OP with Changelog for Build #2.
bbivan said:
Wow....really good news! You are great:thumbup: how is camcorder? Work as well anyway thanks for you hardwork... Cannot wait for download build 2 .... Thanks & congratulation. :thumbup:
Click to expand...
Click to collapse
Thanks. All that's left to resolve is the WebKit lag. Starting to upload Build #2 right now. Build #3 should be in the works very soon. I want Build #3 to be a final stable release, so I'm hoping for more bug reports during Build #2 so that I can work on the remaining bugs for Build #3.
As for camcorder, same issue with other 4.x ROMs for Ace Plus. Native camcorder doesn't work properly, but using third-party apps work.
Well done Liam, you are a great developer!!! Thank you so much....I will try build #2...I hope to see a stable release on our ace plus...
Build #2 is now online! See the OP for the download link.
For bug reports, please include a logcat. Thank you!
Liam D. said:
Build #2 is now online! See the OP for the download link.
For bug reports, please include a logcat. Thank you!
Click to expand...
Click to collapse
Liam D. flash seems don't work.
Please, test in your phone.
Note: If you flash this https://disk.yandex.com/public/?hash=NIIjDsscL7gafATeEm3V188iUzIjmAsixly8YliwBeE= maybe work again.
It's the FIX for the same problem in SpeedMod ROM.
Liam D. said:
I am VERY PLEASED to announce:
That I have fixed the Camera issue on Build #2. Camera is NOW WORKING!
New build will be uploaded later within the week after I have completed my testing.
Click to expand...
Click to collapse
Great Work. Appreciate your Hard Work.
pcomet said:
Liam D. flash seems don't work.
Please, test in your phone.
Note: If you flash this https://disk.yandex.com/public/?hash=NIIjDsscL7gafATeEm3V188iUzIjmAsixly8YliwBeE= maybe work again.
It's the FIX for the same problem in SpeedMod ROM.
Click to expand...
Click to collapse
Hm. That might have something to do with the fix I applied recently for the camera.
Have you tried using the Xposed Module for it? If it works, then I'll put that method into OP for a temporary fix as I work on reverting to the old code. As for your link, it's broken.
Thanks for reporting!
Liam D. said:
Hm. That might have something to do with the fix I applied recently for the camera.
Have you tried using the Xposed Module for it? If it works, then I'll put that method into OP for a temporary fix as I work on reverting to the old code. As for your link, it's broken.
Thanks for reporting!
Click to expand...
Click to collapse
Yap, link broken :/
What module you say?
pcomet said:
Yap, link broken :/
What module you say?
Click to expand...
Click to collapse
This Xposed module: http://repo.xposed.info/module/com.bassel.flashlightfixer
Please try that and tell me if it works.
Liam D. said:
This Xposed module: http://repo.xposed.info/module/com.bassel.flashlightfixer
Please try that and tell me if it works.
Click to expand...
Click to collapse
I fooled me, meant "autofocus" don't work instead of flash.
I'll try flash soon and i say something.
Note: Apollo don't play music! For FIX, use "Omich Player" from PlayStore.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
/* 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.
*/
NOTE
Should you ever face any issues, provide logs (use Google to find out how to gather those). I also need to know what build you're on - hence, you should mention the build number (or at least a date).
Hint: "It doesn't work" is not a bug report and posts like this will be ignored (and eventually removed). To keep the thread clean, try to use DevDB for real bug reports
SUPPORT ME
If you like my work, feel free to buy me a beer.
You can also contribute to CM using gerrit.
DOWNLOAD
CyanogenMod
Important: Informations regarding the new adoptable storage feature.
Screenshots
SOURCE
CyanogenMod
Kernel: CyanogenMod/android_kernel_sony_msm8930 (branch cm-13.0)
XDA:DevDB Information
CyanogenMod 13.0 for Sony Xperia L, ROM for the Sony Xperia L
Contributors
Olivier
Source Code: https://github.com/CyanogenMod/android_kernel_sony_msm8930
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Nightly
Current Stable Version: RC1.2
Stable Release Date: 2016-10-07
Created 2015-11-22
Last Updated 2016-10-10
Not working/broken
NOT WORKING/BROKEN
- everything related to media/audio
- GPS
- FM radio
- Camera
- network types (only 3G works)
- internal storage
Reserved
CHANGELOG
20161004: RC1
- Fixed sound while recording videos (thanks to RonGokhale)
- Fixed sound in FM radio
20160830: BETA3
- Many upstream changes (incl. merge of Android 6.0.1_r61)
- Improved sepolicies
- Replaced the old Browser app with the new, shiny Gello
- Cleaned device tree and restructured it into fragments (thanks to AdrianDC for doing that)
- Adressed security vulnerabities in the kernel
- Switched to the new audio HAL (special thanks to Arne Coucheron, AdrianDC and RonGokhale) - WIP! (please report any audio issues)
20160707: BETA2
- Many upstream changes (incl. merge of Android 6.0.1_r46)
- Removed unnecessary kernel modules and moved the important ones to the kernel
- Cleaned and updated sepolicies & enabled enforcing SELinux (we can now hit the nightlies)
- Reverted to Camera2 since it's more stable and reliable than Snap
20160519: BETA1
- Many upstream changes (incl. merge of Android 6.0.1_r43)
- Fixed camera
- Fixed FM radio (again)
- Enabled zRAM and added various kernel patches for a little performance boost
- Adressed some security vulnerabilities in the kernel
- Switched to the new camera app, "Snap"
20160313: ALPHA5
- Many upstream changes (incl. merge of Android 6.0.1_r22)
- Fixed auto rotation issues
- Fixed some security vulnerabilities in the kernel
20160106: ALPHA4
- Fixed battery LED issues (should be fine now, thanks to AdrianDC)
20151220: ALPHA3
- Fixed network modes (they seem to be swapped, though)
- Enabled FM radio
20151219: ALPHA2
- Fixed internal storage
- Fixed media and audio
- Android 6.0.1
20151122: ALPHA1
- Initial public release.
Key Notes
Flashlight toggle works perfectly. Yay!!
Battery charging LED too works, but expecting CM to break it, again.
If you are going to install gapps, flash it just after flashing CM13. I used pico opengapps, flashed after CM13 booted up, got frequent Setup Wizard and GPServices error. Right then, did a factory reset. Working.
Guys, let's not forget that is a development thread.
It seems like the majority of users with bricked devices have partitioned SD cards.While I can't guarantee anything, this seems to be the only possible reason at the moment. I have been testing CM13 on my C2105 for weeks, but never had that issue. And no, it's not the model number - the differences between C2104 and C2105 are rather minimal and the ROM has been confirmed working on both variants anyway.
Nevertheless, I've locked the thread and removed the download link for now, but just for the future: Don't re-partition your SD cards - in case you have already done so, format your storage before flashing this ROM! Xperia L doesn't have storage galore and the apps get bigger and bigger, I know. But if you aren't satisfied with that you better buy a new device.
Anyway, I'm sorry for the hard bricks.
EDIT: Those who have ended up with hardbricks have probably played around with the new "adoptable storage" feature, it can destroy the emmc.
Thread cleaned per OPs request.
A new build (ALPHA2) is up. Everything should be working, except for bugs mentioned in the second post - although I have been testing the build myself (as usual), I'd appreciate useful feedback. Enjoy, thread reopened...
I might give it a try later today when I get home.
Oh, and what is this "adoptable storage" feature, and how do I know if I have it enabled? I'm afraid of a permabrick since I recently bought this device and I won't be able to buy a new one if something goes wrong...
Edit: Can this be installed with the TWRP from corphish's app?
I installed Alpha 2 (19/12 Build)....
And All Basic Features and My Favorites Apps Are Working Good...
I'm feeling that CM13 is very smooth and fast...
No problem in Power off and reboot to... :highfive:
I'm waiting for Camera Fix... :fingers-crossed:
Thank You So Much.... :good:
Huge improvement
Olivier said:
A new build (ALPHA2) is up. Everything should be working, except for bugs mentioned in the second post - although I have been testing the build myself (as usual), I'd appreciate useful feedback. Enjoy, thread reopened...
Click to expand...
Click to collapse
My review: Flashed it via TWRP and it supports f2fs too... (System was in ext4 though) Boot time was less compared to LP... And yeah everything's great. It's butter smooth. No lags or what so ever! Battery backup is good too... But the only thing I noticed was the network type remains on 3g no matter what i do. Rest all is fine. Fm radio is missing though. Looking forward for camera fix too. Overall a splendid ROM for alpha stage. Also no hardbricks or anything... Rebooted thrice till now and no issues. Great Work.
(Pardon me if i posted in wrong place..... I'm noob in XDA)
Well. the browser force closed for me thrice right after clicking the 'download' button..
Rest its great..
priyank.g said:
Well. the browser force closed for me thrice right after clicking the 'download' button..
Rest its great..
Click to expand...
Click to collapse
The issue is in the browser app itself. Found this on cyanogen forums: http://forum.cyanogenmod.org/topic/...ild-in-browser-crash-when-downloads-anything/
EDIT: If you mean the issue in the ROM
Sent from my LG-H815 using Tapatalk
Another day, another build
ALPHA3 is up, check the third post.
Olivier said:
Another day, another build
ALPHA3 is up, check the third post.
Click to expand...
Click to collapse
Gps works too?
rostifaner said:
Gps works too?
Click to expand...
Click to collapse
Yup. works for me.
Olivier said:
Yup. works for me.
Click to expand...
Click to collapse
Woohoo)) thank you :good:
I tried the Alpha 2 and it was pretty good for an alpha.. Jesus, I was VERY worried during the install, even of the tiniest error.
When it finished I was pretty ****ing relieved that I didn't experience a brick.
The alpha was 'stable'. I mean, things didn't force-close for me constantly, which was the experience for me with other alphas. I can't wait till the camera gets fixed.
Olivier said:
NOT WORKING/BROKEN
- everything related to media/audio
- GPS
- FM radio
- Camera
- network types (only 3G works)
- internal storage
Click to expand...
Click to collapse
I didn't read something about camera issue in this 'Not Working Post'...is it already fixed in Alpha 3?
Xperia_L said:
I didn't read something about camera issue in this 'Not Working Post'...is it already fixed in Alpha 3?
Click to expand...
Click to collapse
Well it says right there...
Not working: camera
Sent from my Taoshan using XDA
CyanogenMod (CM 10.1)
Android 4.2.x & CyanogenMod (CM10.2) Android 4.3.x Note: This is build from source for the device s7560 jellybean Rom, this is the same rom that also works on s7562 device, which is, same as our device in everything except it's a single sim phone.
I tested them on my device and it works the smoothest and fastest, I have ever gone on S duos. OC kernel works good, apart from that this is not recommended for daily users.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.x (Jelly bean), 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.
* these are highly experimental files, for our devices.
*/
About CM
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.
Bugs
Not Working
Rear camera input is rotated in stock camera app (Use a third-party app such as CameraMX) (only in 4.2.2)
Camera only supports 3 megapixels (CameraMX supports 4 megapixels)
Bluetooth is not working
No Mobile network no dual sim support.
Off Mode Charging Doesn't Work
Data usage section in settings is non-existent
FM Radio
Working
Wifi
and everything else other than above list.
Screenshots for CM10.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ScreenShot for CM10.2
Note that this Pic is from a S7562 device and not really a s7560M device
Installation
Copy GApps and CM-Rom ZIPs to your internal SDCard
Boot into Recovery
wipe data factory reset
wipe cache
wipe dalvik cache
format system
Reboot recovery once
Flash CM-Rom ZIP from internal SDCard
Flash GApps zip from internal SDCard
Reboot
Downloads and Links
Thanks jonypx09 and SeannyM Here
CM10.1 Download
Google Apps for Android v4.2.2 (Jelly Bean)
Give thanks to Codename13 here
CM10.2 Download
BA2x kernels
Contributors
@jonypx09
@SeannyM
@Codename13
Miscellaneous Information:
The development of jellybean stopped years ago and it is unsupported until today. it has some major bugs regarding network, bluetooth, offline charging, FM radio. but those of us who use this phone as nothing more than a toy or use wifi for browsing internet, can try these for themselves and see how good this device can perform. Asking devs to help us here is too much and really these bugs aren't easy to solve, I know Because I tried and failed myself. well codename13 has his work saved on github for cm10.2 and anyone who wants to try to be a successful dev can check it here on github
Reserved
Hey
I tried this ROM and it is real smooth.
Had a question is this project ended or we are going to have update in future?
black dark man said:
Hey
I tried this ROM and it is real smooth.
Had a question is this project ended or we are going to have update in future?
Click to expand...
Click to collapse
Sadly, Yes.
right now, nobody is interested in updating this, this is really smooth and fast, and I feel this could be best for our device minus the ril bug. I tried kitkat, but there I know, it's never going to be this smooth, plus most of the apps could run on jellybean, so it's better than staying on ics, which has lesser app support now. the devs of s7560 have avoided this cause of the bug and moved on to cm11. It's better there but for me cm11 is slower than 10.1 too. I do hope someone could try to fix this. I tried, but I don't have that much resources to build a rom and knowledge to sort out these bugs. If i could, I would have done it myself.
@kengnatural and @KlinkOnE if you all can also look on this page
if anyone of you can build a good kernel for this rom it would be good to go and is also much better than cm11 relative to the performance and smoothness part
---------- Post added at 11:41 AM ---------- Previous post was at 11:33 AM ----------
@billysam
thumbs up
and i think there has been a kind of confusion.
those are cm10.1 and cm10.2 but in the main thread where screenshots are posted u have written cm10.2 and cm10.3
balindam bajpai said:
@kengnatural and @KlinkOnE if you all can also look on this page
if anyone of you can build a good kernel for this rom it would be good to go and is also much better than cm11 relative to the performance and smoothness part
---------- Post added at 11:41 AM ---------- Previous post was at 11:33 AM ----------
[/COLOR @billysam
thumbs up
and i think there has been a kind of confusion.
those are cm10.1 and cm10.2 but in the main thread where screenshots are posted u have written cm10.2 and cm10.3
Click to expand...
Click to collapse
Nice to see that there is more than one option to play width. I'd like to say that although a kernel is the essential part of the operating system, in particular Android ecosystem, this itself is not enough to build a full working ROM. In our case i think the kernel we used with CM11 is already working, nice and smooth. There are also stock kernel for ICS and kylesopen kernel. All they could be used here. But for porting the ROM you also should carefully port a lot of native libraries. Bluetooth, radio, etc. That's why the kernel will not solve the bugs. The same situation is for CM11. Kernel is working fine, but some of the native libraries are ported as binary from ICS rom, there are some inconsistencies between higher level subsystem and native libraries, HAL etc.
@billysam, please, investigate the CM11 build, you can take some libraries from there. The RIL part in CM11 is already working (thanks to @m4jonez) you can investigate and reuse that part. The same thing is bluetooth and camera.
balindam bajpai said:
@kengnatural and @KlinkOnE if you all can also look on this page
if anyone of you can build a good kernel for this rom it would be good to go and is also much better than cm11 relative to the performance and smoothness part
---------- Post added at 11:41 AM ---------- Previous post was at 11:33 AM ----------
@billysam
thumbs up
and i think there has been a kind of confusion.
those are cm10.1 and cm10.2 but in the main thread where screenshots are posted u have written cm10.2 and cm10.3
Click to expand...
Click to collapse
there is no native dualsim support in cm10.x
you`ll have to find the right commits from cm11 and adapt it to cm10
KlinkOnE said:
there is no native dualsim support in cm10.x
you`ll have to find the right commits from cm11 and adapt it to cm10
Click to expand...
Click to collapse
i didnt get you?
what do u mean when u say find the right commits?
edit: okay i got you
and if you could just compile or edit the kernel and see if it works as you are a good kernel developer
@balindam bajpai thank you for the corrections and bringing this up with other devs, I tried this rom with Ba2x kernels (link in first post), I flashed all the Ba2x kernels for s7562, they all booted with the above builds but ril, bluetooth camera didn't worked in any case.
@kengnatural and @KlinkOnE
before posting this thread I did a lot of reading and downloaded all the files I could of both these devices CM10.1, CM10.2 and CM11 too. I even tried to download the whole source for JB, but have storage issue on my Linux PC, which is quiet old too, so I can't help in building Rom or kernel for it. I spent my limited bandwidth too but no success.
So, I tried replacing libs from CM11 roms where bluetooth ril and camera where working. the only success I got, the rom stopped flashing the insert sim card error on setup wizard.
couldn't make bluetooth work just by replacing libs, modules, jar .so files, I gave a nice amount of time experimenting with all the files I could think of replacing in this build on my S duos.
Switched basebands too of s7560 on s duos.
I know it's hard to get dual sim support here but single sim will be enough too for starters.?
I think you could tell by the screenshots of the about device above taken on my s duos. even after all this experimenting and not from a developer background, I still have managed to keep my device alive for more experiments. there is also a CM9 thread of s7560 I don't know if you all have noticed this or not http://forum.xda-developers.com/gal...rom-cm9-samsung-galaxy-trend-ace-iix-t2876858
@KlinkOnE
if you could make a kernel compatible with this rom and may be this rom turns out to be the best one
even better than cm11 as already it is much more smooth.
and if you along with @kengnatural can develop this rom
and i and @billysam can help you with the testing part,giving feedbacks and bug reports. @kengnatural thank u for the knowledge given and if could yourself replace the required files and see if ril gets going.
balindam bajpai said:
@KlinkOnE
if you could make a kernel compatible with this rom and may be this rom turns out to be the best one
even better than cm11 as already it is much more smooth.
and if you along with @kengnatural can develop this rom
and i and @billysam can help you with the testing part,giving feedbacks and bug reports. @kengnatural thank u for the knowledge given and if could yourself replace the required files and see if ril gets going.
Click to expand...
Click to collapse
I did tried to change ril related so files along with bluetooth and camera from CM11, and it did stop the error sim msg popping up in CM10 builds, but still didn't worked out network on even single sim(that's what I use).
although I would really like devs to lend a hand on this project, but there should be absolutely no pressure on any devs to work and avoid making request for the same consistently asking for ETA or updates that would hamper their ongoing projects.
You can always count me in for testing, any suggestions here are accepted and I will try my best to take out time for this here with proper error reporting.
@billysam
i guess u are right
and i have already have had a take with one of the developer and i think that they will develop this also but after having fixed all the bugs of cm11,kinda good strategy i think.
so i think this project is till then postponed.
btw thanks to all.
billysam said:
I did tried to change ril related so files along with bluetooth and camera from CM11, and it did stop the error sim msg popping up in CM10 builds, but still didn't worked out network on even single sim(that's what I use).
although I would really like devs to lend a hand on this project, but there should be absolutely no pressure on any devs to work and avoid making request for the same consistently asking for ETA or updates that would hamper their ongoing projects.
You can always count me in for testing, any suggestions here are accepted and I will try my best to take out time for this here with proper error reporting.
Click to expand...
Click to collapse
replacing libs doesn't help anything here.
The rom has to be build from source with the required modifications for dualsim!
As you may have noticed I am even doing nothing cm11 related atm cause I have no time at all.
From my point id say improving cm11 for our device makes more sense.
FFS
Can I try the gapps in this page in the 4.4.4 cm11 rc3 rom?
Because the DevHost links are not at all working for me.
The actual file never gets Downloaded.
So can I try this version of gapps?
RaShx27 said:
Can I try the gapps in this page in the 4.4.4 cm11 rc3 rom?
Because the DevHost links are not at all working for me.
The actual file never gets Downloaded.
So can I try this version of gapps?
Click to expand...
Click to collapse
If you flashed JB GApps to a KK system, chances are:
- They will be installed but with some errors.
- They won't be installed.
Try to download from opengapps.org
Select 4.4 ARM nano or pico package
Sent from my GT-S7562 using Tapatalk
i don't understand you
Bugs
Not Working
Rear camera input is rotated in stock camera app (Use a third-party app such as CameraMX) (only in 4.2.2)
Camera only supports 3 megapixels (CameraMX supports 4 megapixels)
Bluetooth is not working
No Mobile network no dual sim support.
Off Mode Charging Doesn't Work
Data usage section in settings is non-existent
FM Radio
Working
Wifi
and everything else other than above list.
Would this mean that it is as a paperweight with WIFI?
Let's build a new extreme well written software for sduos from ground level .open a whatsapp group first and add all who are interested in sduos discussion +918129494904....
Nevermind!all discussion upon cm 12/13 sduos @Nico belic 605
SduosGt7562 said:
Let's build a new extreme well written software for sduos from ground level .open a whatsapp group first and add all who are interested in sduos discussion +918129494904....
Nevermind!all discussion upon cm 12/13 sduos @Nico belic 605
Click to expand...
Click to collapse
so u are going to build a ROM from scratch(ground level)
are you a developer or have any prior experience?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 11
Disclaimer
Upon flashing this ROM, you have voided your warranty. The developers are not held responsible for any problems or damage that may happen to your device. Please do some research first if you have any concerns regarding the features and bugs of this ROM. YOU have chosen to take this risk. You have been warned.
Downloads
Alpha
These are meant for development purposes and for the curious who would like to see the current progress.
Alpha 1
Beta
These are stable enough for daily use, which gives a near-smooth experience with most features working.
Beta 1
Beta 2
Beta 3
Beta 4
Beta 5
Beta 6
Stable
These speak for themselves.
Stable 1
Nightlies
These are updated everyday, more or less stable and with the latest bug fixes and features, but may break your device. Use with caution.
I understand the consequences, take me there now please.Bugs
These are the current bugs in the latest builds.
NFC (S6310N only)
RIL (S6312 only)
Video playback (Fixed in the nightly builds)
Camera
[See more or file a new bug report.]
FAQ & Troubleshooting
ETA for new release?
Don't ask, just wait.Why did make a new thread?
So I could update it and reach more people.Can X feature be added?
We might add it. File a feature request.Can I help with the development?
You can if you are willing, but PM me first before doing anything else.Stuck on CyanogenMod loading screen?
Make sure you have cleared your davik-cache, cache, and data partition before flashing.Getting a bootloop?
Make sure that you have downloaded the right ROM for your device.AOSP Keyboard force closes?
This is a bug within the app itself, we have no choice but to wait for the gapps developers to fix it.My problem X still persists even after doing the necessary steps, what now?
File a bug report, and include every detail of it (e.g. logcat, dmesg, etc.)
Do note that this is a development discussion, so refrain from posting anything unnecessary. If you want to thank us, just smash that thanks button.
XDA:DevDB Information
CyanogenMod 11 S63xx, ROM for the Samsung Galaxy Young S6310
Contributors
lesleyxxx15, NV-Dev, techyzen101
Source Code: https://github.com/S6310-Development
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: None
Based On: CyanogenMod
Version Information
Status: Abandoned
Current Stable Version: 1
Stable Release Date: 2016-05-28
Current Beta Version: 6
Beta Release Date: 2015-09-18
Created 2016-06-11
Last Updated 2016-08-01
Changelogs
Beta 1:
Fixed RIL
Overclocked CPU to 1.3Ghz
New device-tree and vendor
Fixed SELinux
Beta 2:
Fixed FC in some apps
Use libwebcore instead of webviewchromium
Fixed rotation
Change bootlogo
Beta 3:
Fixed MTP
The density is again 160DPI
The Audio HAL has been updated so the CAD driver is used
Fixed Equalizer
The browser works correctly
Ramdisk has been modified so the CAD driver works.
audio_policy.conf was updated
Added F2FS Support and enabled it
Added UHID Driver and enabled it
Beta 4:
Updated device-tree
Updated vendor
Fixed mini bug on browser
Added CMAccount
Beta 5:
Updated Audio (No noticable change tho)
Updated Camera (Still not fixed but getting closer)
Fixed Bluetooth
Beta 6:
Offline charging fixed (only when trying to boot with cable plugged in hangs on offline charging and when plugged in to usb it starts booting)
Fixed bug causing Xposed to not work
Kernel 3.4.98
Overclocked GPU to 192 MHz (some users experienced problems with this)
Fixed a few bugs related to Bluetooth
Added CMAccount again
Stable 1:
Updated CAD definitions (by @techyzen101), this fixes audio related bugs.
Updated kernel to support display-caf which is now being used (this broke video playback)
Offline charging now fully working (again @techyzen101)
Removed the camera binary to fix an issue with deep sleep
Updated BlueZ to 5.38 (thanks @NV-Dev)
Thanks and Keep up the great work...sure this will make the ways easier for cm 12 and cm 13
elprince_99 said:
Thanks and Keep up the great work...sure this will make the ways easier for cm 12 and cm 13
Click to expand...
Click to collapse
Don't forget 14
Great ! Testing it right now !
lesleyxxx15 said:
Don't forget 14
Click to expand...
Click to collapse
Ofcourse...you are a big developer and we all support you
with action launcher, my favorite, and a few mb more zram. would be nice if we could overclock this cpu too.
**edit: more photos. with a little overclocking too, the phone doesnt lag at all, but forget the battery. in 6 hours without even using much the phone , battery is dead and need recharcge.
~wave to unlock feature also is working like a charm.
What is the order of (fixing ril for s6132) in the list of bugs to be fixed ?
elprince_99 said:
What is the order of (fixing ril for s6132) in the list of bugs to be fixed ?
Click to expand...
Click to collapse
First Camera then Dual Sim
lesleyxxx15 said:
First Camera then Dual Sim
Click to expand...
Click to collapse
Thanks for your effort and good luck in fixing bugs
Hope my phone back normally on days, today go to service, so I'll flash with this ROM again. I agree , dev must focus on cm11 so everything work like stockrom after that cm12 and 13, I like cm12, Alive colors, and maybe cm13 is more interesting :good:
Do best devs
beta 1 sais the cpu is overclocked but at s6310 i get max 1008mhz. can s6310 be overclocked too ? it is too slow at 1008
kessaras said:
beta 1 sais the cpu is overclocked but at s6310 i get max 1008mhz. can s6310 be overclocked too ? it is too slow at 1008
Click to expand...
Click to collapse
The overclocks were removed as of Beta 5 as I started my own kernel project. This kernel made 5.0+ and much more possible. Stable 3 might get overclocks, undervolting etc.
@lesleyxxx15 can you give a link for working gapps please? Thanks
razvangrig said:
@lesleyxxx15 can you give a link for working gapps please? Thanks
Click to expand...
Click to collapse
http://opengapps.org/
Pick ARM, 4.4 and nano.
Any feedback? I wanna try this CM rom for my lil bro's SGY but afraid if it still not for daily use.
Sent from my GT-N7000 using XDA-Developers mobile app
Camera is a bug? Why it is stable? Can we use cam now in this version?
Sorry because it is only my opinion!
Sent from my GT-S6310
JerwinSayat said:
Any feedback? I wanna try this CM rom for my lil bro's SGY but afraid if it still not for daily use.
Sent from my GT-N7000 using XDA-Developers mobile app
Click to expand...
Click to collapse
phamngocduy.1998 said:
Camera is a bug? Why it is stable? Can we use cam now in this version?
Sorry because it is only my opinion!
Sent from my GT-S6310
Click to expand...
Click to collapse
The Stable build in the OP is fine for daily usage. All bugs which are found are there.
It's up to you guys to see if you really need the camera or want to watch vids etc.
Stable 2 will be released when the Camera works and will be for all devices (S6310, S6310N, S6312)
lesleyxxx15 said:
The Stable build in the OP is fine for daily usage. All bugs which are found are there.
It's up to you guys to see if you really need the camera or want to watch vids etc.
Stable 2 will be released when the Camera works and will be for all devices (S6310, S6310N, S6312)
Click to expand...
Click to collapse
I see. Maybe I'll wait for the next version. Goodluck dev! You can do it hehe
Sent from my GT-N7000 using XDA-Developers mobile app
Hi Les, move sensor doesn't work whit last nightly build.
Work fine whit Stable rom
Hi,
This is a port of Sailfish OS to the Motorola G 2014 LTE (aka thea). If you are looking for Sailfish OS for the regular Motorola G 2014 (aka titan) look here Sailfish OS for titan
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
Sailfish OS Version 2.x (work in progress)
ROM cm-12.1-20151117-SNAPSHOT-YOG7DAO1K5-thea.zip
Beta 8: sailfishos-thea-release-2.1.2.3-guhl171102.zip (current)
Beta 7: sailfishos-thea-release-2.1.0.11-guhl_170604.zip (old)
Beta 6: sailfishos-thea-release-2.0.5.6-guhl170218_obs.zip (old)
Beta 5: sailfishos-thea-release-2.0.5.6-guhl170214_obs.zip (old)
Beta 4: sailfishos-thea-release-2.0.5.6-guhl170209_obs.zip (old)
Beta 3: sailfishos-thea-release-2.0.5.6-guhl170205_obs.zip (old)
Beta 2: sailfishos-thea-release-2.0.5.6-guhl170122.zip (old)
Beta 1: sailfishos-thea-release-2.0.5.6-guhl170117.zip (old)
Installation:
Remark: The installation of the correct CM (12.1 for SF 2.x) image is only necessary once. So if you already did this the first time you can skip steps 2 and 4.2
1. Boot into your custom Android Recovery and make sure that the sdcard is mounted
2. Upload the CM release: adb push cm-12.1-20151117-SNAPSHOT-YOG7DAO1K5-thea.zip /sdcard1/
3. Upload Sailfish OS: adb push sailfishos-thea-release-2.1.2.3-guhl171102.zip /sdcard1/
4. In the Recovery on the device:
4.1. Clear data and cache (factory reset)
4.2. Install the CM release by picking the CM image (this is needed so that the correct version of the binary libraries and firmware files are in place)
4.3. Install Sailfish OS by picking the SFOS image (this will take quite some time)
5. Reboot the device
After the initial boot (that will take some time) the language selection and initial setup will show.
After that it will take a while and then the Jolla tutorial should come up. You can skip the tutorial if you want by clicking the corners of the screen in the following sequence: Top-Left, Top-Right, Bottom-Right, Bottom-Left.
Remarks
Recorded-Video playback: Works but uses a nasty hack that might have stability and security effects.
Known not to work
There is an issue switching from video-playback to camera. Sometimes the camera app hangs afterwards -> reboot.
Change-log:
Current Version
Version 20171102
updated to version 2.1.2.3 (complete rebuild and code cleanup)
fixed screen startup on reboot (aka lipstick-hack) -> stable reboots
probably the best and most stable build up to now.
Version 20170604
updated to version 2.1.0.11 (fixes also USB "Alwas ask" mode)
Version 20170218
fixed sdcard mounting
Version 20170214
Proper fix to sensorfw accepted upstream -> removed sensor hack
Fixed camera startup and video recording. Works on first start now and does not crash on restart
Hack to make playback of recorded video work.
Version 20170209
Fixed acceleration and rotation sensor
improved video recording - still not working properly
Version 20170205
Fixed and added FM-Radio
added Mozilla Location Service as location provider
built on mer OBS - preparation for OTA updates in the future
Version 20170122
Added Bluetooth
Version 20170117
Initial release of Beta 1
Credits:
mal, sledges, MisterMagister - et al. from the #sailfish-porters IRC channel on freenode
These guys are doing amazing work and their competence and readiness to help is really inspiring.
Without their support this would not have been possible!
Have fun - Guhl
Nice works, congrats
I will test soon
Thanks!!
Beta 2
Hi,
I uploaded Beta 2.
Bluetooth is working,
Video recording is not - do not try!
Have fun - Guhl
Nice ! That's awesome there is still support for this device !
Just curious, did you use anything from my GitHub or is everything outdated ?
Mavireck said:
Nice ! That's awesome there is still support for this device !
Just curious, did you use anything from my GitHub or is everything outdated ?
Click to expand...
Click to collapse
Hi Mavireck,
I did see your work on this of course and I also looked at MisterMagister and your github sources.
But in principle I did this port from scratch as most of the things are outdated as you already assumed.
I am building titan already on OBS nemo:devel:hw:motorola:thea and am preparing to create the next fixes and releases as OTA instead of complete builds.
And of course I would be very happy if you have some spare time and join me in this port effort. (my resources are on github of course).
Have fun - Guhl
guhl99 said:
Hi Mavireck,
I did see your work on this of course and I also looked at MisterMagister and your github sources.
But in principle I did this port from scratch as most of the things are outdated as you already assumed.
I am building titan already on OBS nemo:devel:hw:motorola:thea and am preparing to create the next fixes and releases as OTA instead of complete builds.
And of course I would be very happy if you have some spare time and join me in this port effort. (my resources are on github of course).
Have fun - Guhl
Click to expand...
Click to collapse
I don't think I would be able to help... I am still new to all this kind of stuff (I didn't even used Linux before).
I had just followed the instructions and I stole some fixes here and there but I wasn't able to fix the issues that weren't documented.
I really don't have time now (final exams are coming) but maybe later I will re-download the sources and have a look.
P.S. I don't even have my Moto G anymore : I lent it to a friend.
Beta 3
Hi,
I released Beta 3 and updated the OP.
See changelog in OP.
Have fun - Guhl
Beta 4
Hi,
I released Beta 4.
It mainly fixes the sensors (acceleration and rotation). As Motorola did a real nasty hack in the acceleration kernel driver and the closed source sensor-library I also had to do a nasty hack to get the sensors working. For now this is done by a script that monitors the screen on/off state and also enables/disables the sensor chip that is responsible for acceleration, magnetometer and compass.
If you are interested see here:
https://github.com/guhl/droid-config-thea/commit/27dff552d1d655a44917ab68536c27d55eeb2b2f
I will integrate this functionality into the regular Sailfish OS (mer) sensorfw service to remove the hack-script and try to get that integrated upstream.
Have fun - Guhl
Hi
I install the rom on my thea and this is my report of bugs
- Can't access to my external sdcard (maybe the format of the sd is not support for the rom) I try mount in options but not work
-When shutdown my phone ( not restart) and re start/on , I get bootloop, in the logo motorola, led notifications on and not loading. (My solution in the recovery, wipe davilk/art and cache, and works again)
Works fine to me
Wifi,bluetooh, sensors, Signal, sync account to google, no fc
I not test gps, calls
Sorry for my English is regular
Nice rom and project!! Waiting for more
Regards!
Beta 5
Hi,
I uploaded Beta 5 and changed the OP accordingly.
In principle all functionality should be working now. See the OP for some remarks.
Be warned again, that the hack that is used to fix recorded video playback may have stability and security side effects. The hack basically removes a check in the OMX decoder that the allocated video buffer does not have the same size as the expected size (it is smaller). This may enable buffer overruns with the usual side effects. So if you want to be careful: Do not play videos from sources you don't trust
Have fun - Guhl
Lukasm7 said:
Hi
I install the rom on my thea and this is my report of bugs
- Can't access to my external sdcard (maybe the format of the sd is not support for the rom) I try mount in options but not work
-When shutdown my phone ( not restart) and re start/on , I get bootloop, in the logo motorola, led notifications on and not loading. (My solution in the recovery, wipe davilk/art and cache, and works again)
Works fine to me
Wifi,bluetooh, sensors, Signal, sync account to google, no fc
I not test gps, calls
Sorry for my English is regular
Nice rom and project!! Waiting for more
Regards!
Click to expand...
Click to collapse
Hi,
thanks for the feedback.
I know that the reboot does not work some times. I think that even without cleaning the cache it should work after you booted to recovery once. I have no idea what is causing this but maybe we can find some more hints.
I will look into sdcard mounting, never tried that
Have fun - Guhl
Beta 6
Hi,
Lukasm7 said:
Hi
- Can't access to my external sdcard (maybe the format of the sd is not support for the rom) I try mount in options but not work
Click to expand...
Click to collapse
I uploaded Beta 6 and updated the OP to fix the sdcard mounting.
Have fun - Guhl
guhl99 said:
Hi,
I uploaded Beta 6 and updated the OP to fix the sdcard mounting.
Have fun - Guhl
Click to expand...
Click to collapse
Thanks, I test soon and report others problems or bugs , nice works!!:good:
I Test the last update, everything works fine, very smooth and fast
External sdcard works perfectly
The only drawback is the compatibility of apps with android, the rest is correct and works fine
Good rom , and I hope someday you can use android apps
Regards!
Lukasm7 said:
I Test the last update, everything works fine, very smooth and fast
External sdcard works perfectly
The only drawback is the compatibility of apps with android, the rest is correct and works fine
Good rom , and I hope someday you can use android apps
Regards!
Click to expand...
Click to collapse
Hi,
Thanks for the feedback.
I will try to include sfdroid (https://wiki.merproject.org/wiki/Adaptations/libhybris/sfdroid) in the next build. This is not as stable and convenient as Alien-Dalvik but Alien-Dalvik must not be included in Sailfish Ports. But sfdroid should give you some Android support.
Have fun - Guhl
Hello,
very nice, everything works.
I am waiting impatiently the next release were can be installed Android app.
Thanks,
Ferenc.
Solved: install some libraries for exfat.
_______________________
Hello,
I have one question, how I mount the SD-card?
Best regards,
Ferenc.
GPS and Magnetometer don't work
Dear Guhl,
thanks for the great job of porting Sailfish to the thea device.
1. I found that in beta6 neither GPS nor magnetometer work. I am wondering if it is only me or if it is a general problem.
2. Besides that I am having an issue with the mobile data connection in general. I am using a DATA ONLY card of dmm.com in Japan. Sometimes I can get a connection, but the signal strength is shown as 0. Randomly I get disconnected.
Probably this is an Sailfish general issue and not related to this particular port.
Background: japanmobiletech.com/2013/08/improved-fix-for-docomo-mvno-data-only.html
Thanks & Regards, azak2000
azak2000 said:
Dear Guhl,
thanks for the great job of porting Sailfish to the thea device.
1. I found that in beta6 neither GPS nor magnetometer work. I am wondering if it is only me or if it is a general problem.
2. Besides that I am having an issue with the mobile data connection in general. I am using a DATA ONLY card of dmm.com in Japan. Sometimes I can get a connection, but the signal strength is shown as 0. Randomly I get disconnected.
Probably this is an Sailfish general issue and not related to this particular port.
Background: japanmobiletech.com/2013/08/improved-fix-for-docomo-mvno-data-only.html
Thanks & Regards, azak2000
Click to expand...
Click to collapse
Hi,
what software are you using to test GPS/magnetomther? I am using GPSInfo for GPS testing and don't have any issues with GPS (after turning on location in settings).
I will have look at that patch and see how this applies to Sailfish (ofono - the telephony stack of Sailfish OS) but I might need your help there as I probably will need some logs from your phone.
Maybe you can try to find me on the #sailfishos-porters on the freenode IRC system (but probably our timezones are not very compatible as I am in UTC+2)
Have fun - Guhl
todobarato said:
Hello,
very nice, everything works.
I am waiting impatiently the next release were can be installed Android app.
Thanks,
Ferenc.
Click to expand...
Click to collapse
Hi,
I am sorry to tell you that I gave up the effort to run SFDroid on the thea build.
The devices simple and easy does not have enough RAM to allow this to work. SFDroid basically really means (and that is a big difference to the AlienDalvik that is running on the Jolla devices) that SF and Adroid are really running side by side (Android is technically running in a window) and that just does not fly with this device.
As I said, sorry to tell you this and I can assure you that this is frustrating for me too as I spent quite some time on this, but I will not release a SFDroid build for the thea.
Have fun - Guhl
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are beta builds!!! Stuff may be broken/missing/jank!!! You have been warned.
[ROM][AOKP 8.1/OREO][HLTE] AOKP Oreo for Galaxy Note 3 (Unified) Beta Builds
These are beta builds!!! Stuff may be broken/missing/jank!!! You have been warned. Again.
Code:
*** Disclaimer***
Your warranty is now void!
I am not responsible for damages caused by this ROM
YOU are choosing to install it!
If you have any concerns about potential issues or features with this ROM, do your research!
If you accuse me of causing problems with your device, you WILL be ridiculed!
Read the above warnings again! These are BETA builds!
They are [B]NOT[/B] feature-complete, nor are they guaranteed to run!
By installing them, [B]YOU[/B] are assuming the risk of any potential problems!
Introduction
AOKP is a ROM developed by TeamKang, based on AOSP with magical unicorn bytes (awesome features) baked right in!
hlte builds are for hltexx/hltespr (SM-N9005/SM-N900P)
hltechn builds are for hltezm (SM-N9008V)
hltekor builds are for hltektt/hltelgt/hlteskt (SM-N900K/SM-N900L/SM-N9005 (SK Telecom ONLY))
hltetmo builds are for hlteusc/hltetmo/hltevzw/hltecan (SM-N900R4/SM-N900T/SM-N900V/SM-N900W8)
Features
Android 8.1 Oreo
OMS/Substratum Support - Theming baked right in
SU baked in - No need for SuperSU/Magisk (Unless you want them!)
ROMControl App - A centralized place to manage all almost all the cool features Magical unicorn Bytes!!
More features coming soon! (P.S. Asking for ETA's is bad, unless you like NOT getting new features! )
Click to expand...
Click to collapse
Known Issues
Bluetooth does not work with some devices - This is a known issue that also affects LineageOS-15.1 Fixed?
You tell me! I have limited testing time, so the more reports I get the better. Please see below for proper issue reporting!
Click to expand...
Click to collapse
Proper Issue Reporting
Make sure you are seeing the issue on a CLEAN install! If the problem pops up after a dirty flash, wipe data/factory reset and see if it still happens before reporting it
Make sure you have not flashed anything extra, such as 3rd party kernels, SuperSU, Magisk, Xposed, etc. These extra packages can cause their own issues. As above, try a full wipe and then only flash the ROM package and Gapps package, and see if the issue persists before reporting
In your report please include the following:
Issue you are seeing, and how to recreate it
Logcat/kmesg from right after the issue if possible
Build date of ROM you are running
Gapps package you have installed
Click to expand...
Click to collapse
Installation instructions
Backup your data! (nandroid, TiBu, etc.)
Wipe Data/Factory Reset (You did backup, right?)
Flash ROM
Flash GAPPS
Wipe Cache/Dalvik Cache
Reboot
Click to expand...
Click to collapse
Download
shane87 AndroidFileHost page:
shane87's AFH page for hlte Oreo Builds (BETA)
shane87's AFH page for hltechn Oreo Builds (BETA)
shane87's AFH page for hltekor Oreo Builds (BETA)
shane87's AFH page for hltetmo Oreo Builds (BETA)
Source:
AOKP Source
Click to expand...
Click to collapse
Changelog
Code:
[B][U]Detailed changelogs between each version can be found at download link[/U][/B]
[B][U]Current changelog: 07/21/2019[/U][/B]
*[fix]BT bug fixed......again......maybe? lol
*[update]Latest AOSP/LOS upstream changes (No AOKP changes since last build - We are all focused on Pie, when we have time!)
[B][U]Changelog: 07/06/2019[/U][/B]
*[fix]BT bug finally squashed! - I hope anyway, let me know guys!
*[update]Latest AOSP/AOKP/LOS upstream changes
[B][U]Changelog: 12/09/2018[/U][/B]
*[fix?]Changes in hardware/samsung (6 commits) - MAY fix BT issues!
*[update]Latest AOSP/AOKP/LOS upstream changes
[B][U]Changelog: 11/18/2018[/U][/B]
*[fix?]Set proper WBS sample rate - MAY fix BT issues!
*[update]Update to Android 8.1_r50 base
*[update]All upstream changes since 09/16
[B][U]Changelog: 09/16/2018[/U][/B]
*[update]Update to Android 8.1_r46 base
*[new/update]Add SystemProfiles QS Tiles
*[fix]Fix some QS tiles, remove some deprecated QS Tile code
*[fix?]Fix spacing in bluetooth_vnd.txt, [i]possible[/i] BT issue fix?
*Full changelog available at download link
[B][U]Changelog: 08/19/2018[/U][/B]
*[fix]Remove reference to mIsTap and Handler in absListViewWidgets.java (frameworks/base) - Fixes ListView mod widget issue
*[fix]Camera regression from 08/12 build fixed - No clue what happened, but everything is working again.
*[update]Add QS animation options to ROM Control
*[update]Add QS title hide option to ROM Control
*[update]Add AOKP logo on status bar option to ROM Control
*Full changelog available at download link
[B][U]Changelog: 08/12/2018[/U][/B]
*[fix]su issues from previous build fixed
*[update]Revert soundboost to stop speaker distortion [update]SoundBoost mods available at dl links!
*Full changelog available at download link
[B][U]Changelog: 07/31/2018[/U][/B]
*[update/fix?]Remove CarrierConfigs from hlte/hltetmo device trees; CarrierConfigs was duplicated in msm8974-common
*[update/fix]Remove vendor security patch level from device trees, move to common tree
*Full changelog available at download link
[B][U]Changelog: 06/24/2018[/U][/B]
*[update]Use mpdecision from G900FXXU1CRA2_G900FOXA1CRA2_BTU
*[update]Drop lib_cutils_atomic shim (was only needed for old mpdecision)
*[fix?]Changing mpdecision and dropping the shim [B][U]SEEMS[/U][/B] to have fixed rotation on LOS, hopefully fixed for us
*Full changelog available at download link
[B][U]Changelog: 06/03/2018[/U][/B]
*[fix]Boost sound levels across all devices
*Full changelog available at download link
[B][U]Changelog: 05/14/2018[/U][/B]
*[fix?]Commit pulled in from AOKP source to fix camera recording issues.
*[update]Latest changes from AOKP source
*Full changelog available at download link
[B][U]Changelog: 05/06/2018[/U][/B]
*[update]Minor changes to QS header images support
*[new]Scrollable QS tiles
*[new]Add builds for hltechn/hltekor/hltetmo
*Full changelog available at download link
[B][U]Changelog: 4/30/18[/U][/B]
*[fix?]Changes to phone call audio routing, may help BT phone audio issues
*[fix?]New overlay that may help with auto-rotation bug
*[new]Customizable header images
*Full changelog available at download link
[B][U]Changelog: 4/23/2018[/U][/B]
*[new]Initial AOKP Oreo Beta release for hlte
Thanks To/Credits
TeamKang
tdm
LineageOS
@stonedead - For finding sensor batching overlay; a potential rotation bug fix!
PayPal Donations and thanks are always appreciated!
XDA:DevDB Information
Oreo Android Open Kang Project for Samsung Galaxy Note 3 (HLTE), ROM for the Samsung Galaxy Note 3
Contributors
shane87
Source Code: http://aokp.co/source/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP 3.2.1-1
Based On: AOKP
Version Information
Status: Beta
Current Beta Version: 2019-07-21
Beta Release Date: 2019-07-21
Created 2018-04-24
Last Updated 2019-07-21
Reserved
As far as an update schedule goes, I will TRY to do weekly builds with the latest commits. I will also TRY to pull in pending commits when possible, assuming I can get them to build.
Nice.. Keep it up :good:
Sorry, can you tell me if the NFC and Bluetooth calls work? Thank you
Ottobrerosso1977 said:
Sorry, can you tell me if the NFC and Bluetooth calls work? Thank you
Click to expand...
Click to collapse
I don't know about nfc, as I never use nfc, but I can confirm that Bluetooth calls work, at least for some Bluetooth devices. I have a Plantronics Legend bt headset, and I can make Bluetooth calls on it. With that being said, I have received reports of some bt devices not working, so ymmv
Button backlight, just as in Nougat AOKP, doesn't work at all. Only in the button settings menu does it come on. They work fine on RRO or LA15.1.
That's what i've found so far.
I'm testing your build to see if the infamous rotation bug from LA15.1 and RRO is present in AOKP and so far it looks good but i need more time to test it.
Running clean install of AOKP with internal root and 23-04 GApps Mini FYI.
Imprezzion said:
Button backlight, just as in Nougat AOKP, doesn't work at all. Only in the button settings menu does it come on. They work fine on RRO or LA15.1.
That's what i've found so far.
I'm testing your build to see if the infamous rotation bug from LA15.1 and RRO is present in AOKP and so far it looks good but i need more time to test it.
Running clean install of AOKP with internal root and 23-04 GApps Mini FYI.
Click to expand...
Click to collapse
Thanks for the report! I'm aware of the button backlight issue as well, I didn't include it in the know issues since it was a carryover from Nougat. I have had a report of rotation issues from Oreo builds, not sure if it affects everyone or just some people, but I am looking into a fix by trader418 that was mentioned to me. By LA15.1, are you referring to LineageOS 15.1? I'll see if I can dig something up on the button backlight issue.
[Edit]
Also, the GApps Mini you are running, is it from OpenGApps?
[/Edit]
shane87 said:
Thanks for the report! I'm aware of the button backlight issue as well, I didn't include it in the know issues since it was a carryover from Nougat. I have had a report of rotation issues from Oreo builds, not sure if it affects everyone or just some people, but I am looking into a fix by trader418 that was mentioned to me. By LA15.1, are you referring to LineageOS 15.1? I'll see if I can dig something up on the button backlight issue.
[Edit]
Also, the GApps Mini you are running, is it from OpenGApps?
[/Edit]
Click to expand...
Click to collapse
Yup OpenGApps Mini. And yeah i meant Lineage. It for some reason always autocorrects a single letter L to LA..
I don't know what the rotation issue is. I mean, some people have it a lot, like me, and some people like vidwhal himself cannot for the life of them recreate it. It has something to do with the accelerometer that just stops giving any values. And so far, it seems that your AOKP build is the most stable so far in terms of rotation. I'm going to continue to set up the ROM with my apps and preferences and i'll see if it keeps working.
Edit: Blast it.. it looked so promising.. didn't have any rotation issues for hours.. and suddenly out of nowhere it stopped working again completely and accelerometer has once again stopped giving any values in Sensors Mutlitool...
Ok, what did i do.. ehm.. installed some apps like chrome, and substratum.. customized my homescreen with the shortcuts i use.. loaded up BigBlu in substratum (works perfectly with AOSP mode btw.) installed adaway (root), used titanium backup (root) to restore my Steam app (so that I don't have to re-activate the steam authenticator), loaded up adaway and thats when i noticed chrome had stopped rotating when i wanted to test adaway..
Was about to reboot into recovery to install xposed v90 beta3 and Gravitybox O so i can center my clock in the statusbar and rebind the back button long press to flashlight but i guess that doesn't really make much sense now that it has stopped working..
Funny thing is, not even a full reboot will fix it. Once it stops working.. it's just done for. With a full power off and reboot it will work for a few seconds after boot but that stops again.
I do have to add on a positive note, i have never had a Oreo rom THIS ridiculously smooth and quick. This ROM runs amazing.. And it has VERY low battery drain when in use. It drains even slower when just using the web or installing stuff than even the best TW6.0 ROMs do.. Incredible. It easily rivals or beats RRN 5.8.5 in terms of smoothness and responsiveness.
Congrats on your new thread bro. It's getting into a right direction now @shane87. So glad to woke up from sleep and seeing the auto rotation still works.
Usually the auto rotation failed within minutes after fiddling with google maps on previous test build and on other oreo rom. Will see it further, hopefully the issue is gone for good now.
Thanks..
Edit: really a one crazy bug this sensor issue. It happening again after a reboot ?
Now that you mentioned it.. I did also reboot before it happened again. It was fine for hours even after maps and setting up the entire ROM but after I applied my substratum theme I rebooted to make sure it applied to all open apps as well and that's when it started again..
I did make a full nandroid of the failed system.. So if you want me to test something I can just put that back.
You guys with the rotation bug, I'm looking in to a possible fix by trader418 that was mentioned by another one of my testers. I have to do some digging and see if I can find how he fixed it. It's so odd. On Nougat, my wife's Note 3 (my only test device) never had the rotation bug. I haven't ran Oreo on it enough to see if it has the rotation bug on Oreo, though I may do that this weekend.
One question for those experiencing the rotation bug: what model is your Note 3?
shane87 said:
You guys with the rotation bug, I'm looking in to a possible fix by trader418 that was mentioned by another one of my testers. I have to do some digging and see if I can find how he fixed it. It's so odd. On Nougat, my wife's Note 3 (my only test device) never had the rotation bug. I haven't ran Oreo on it enough to see if it has the rotation bug on Oreo, though I may do that this weekend.
One question for those experiencing the rotation bug: what model is your Note 3?
Click to expand...
Click to collapse
N9005 here..
I have zero issues on any Nougat ROM as well. That's what makes it frustrating to fix.
Mines also a N9005.
I cannot flash the patched zip file by dual boot patcher
It gives this error logs attched
Im using latest twrp 3.2. thanks
Kalhan said:
I cannot flash the patched zip file by dual boot patcher
It gives this error logs attched
Im using latest twrp 3.2. thanks
Click to expand...
Click to collapse
From the errors given in the log, the multiboot patcher did not patch the zip file correctly. All of the errors were from the zip file being corrupted. So either the file was corrupted during download, or during patching.
With all of that being said, I can't help with issues on dualboot setups. I have never used any of the dualboot setups. Any issues with dualboot need to be taken to the dualboot thread.
thanks good as a daily driver already
Works with N900T?
Par.10 said:
Works with N900T?
Click to expand...
Click to collapse
No, N900T has it's own device tree and separate builds. This is for hlte devices, N9005 and N900P
Alright guys, I have been doing some digging into @trader418 and I can't find anything in particular that helps the rotation bug. In his unofficial Lineage 14 thread, he mentions some cm/los updates that fixed the rotation issues, but doesn't mention the exact commit. Also, it sounds like those changes should already be in these builds, since AOKP's hlte device trees, and kernel source, are forked from LineageOS trees. And I do make sure to pull in the latest LOS changes. So I am still stumped on the rotation bug. On to better news. I have just finished a new build, with the latest AOKP changes synced in. I also pulled in some open commits that add customizable header image support. Along with a few open commits from LOS, mostly to do with phone call audio, so hopefully that may help with BT issues. I am going to do some personal testing before I upload, so be patient, new goodies are on their way!