{
"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"
}
Glad to share with you my builds of CyanogenMod 13.0 (Android 6.0 Marshmallow) for Nexus 4 (mako).
These will probably become obsolete when CM will officially release nightlies for our device, but if as me you can't wait, you can flash it as usual zips.
It is important to note that *at this time of writing* (october 2015), things are not that stable in CM sources. I fixed various issues to make this, and I deeply test everything I build. So, even if I plan a release every day or two (and also depending of my free time in life), nothing will be out if it is too much unstable, I release only "usable" builds.
[About this build]
- Require bootloader/radio from Lollipop minimum
- Contains all CM (kernel, system, ... )
[Note before installation]
- I suggest you to backup your app data with Titanium Backup if you want to restore your apps later
[Downloads]
* Build 2015-12-21
- Build 2015-12-16
- Build 2015-12-09
- Build 2015-12-05
- Build 2015-12-01
- Build 2015-11-28
- Build 2015-11-24
- Build 2015-11-18
- Build 2015-11-15
- Build 2015-11-11
- Build 2015-11-05
- Build 2015-11-02
- Build 2015-10-31
- Build 2015-10-28
- Gapps (Google Apps) ("Micro" gapps works pretty fine on mine).
[How to Install]
- Boot in recovery (TWRP - please use latest)
- Wipe Data, System, Cache, Dalvik-cache
- Install the ROM
- (Optional) Install gapps
- Reboot. If TWRP prompt you to install SuperSu, deny it.
"But hey! I want Root !!"
So you want root on your Nexus 4 !
At time of writing this (october 2015), root doesn't work *from scratch* Marshmallow/CM kernel. So I included into this, "StephanMc Kernel" for mako, which is basically the same "stock" kernel (the CM one is stock-based) with SELinux set as permissive to allow root. No more adds or tweaks, just a root-possible stock kernel.
All you have to do is install SuperSu and it is good to go.
- Download SuperSU Beta
- Flash them Super Su
- Reboot
- Enjoy, you're now rooted !
[Some recommandations]
- Enable Developer Options: Settings -> About -> tap 7 times on Build number
- Enable USB Debbuging
- Enable Offline APK installations: Security -> Unkown sources
[About Titanium Backup]
- Titanium Backup is fixed since build 2015-11-05
[Where is System Ui Tuner ?]
- Expand the Notification bar until you see the Settings icon (on top right corner)
- Hold on the icon for about 5 seconds
- Congrats! You can find System UI Tuner menu into Settings -> just under "About phone" menu
[About Snapchat ? ]
- Snapchat crashes at login with Marshmallow. You can workaround this by downgrading to v9.9.0 (google it), then log in the app. Once done, you're free to update it as usual if you want.
[Screenshots]
- See attachments
[Working / Known issues]
** Not working **
- (Annoying) When In landscape view, notification panel redraw itself also on navigation bar (fixes coming soon)
- Switching from 3G to 2G network seems not working (fixes coming soon)
** Working **
- Everything else
- Some gapps can lead you to wierd "force closes", please make sure you choose a working one.
- Any other issue found ? Let me know
If an application crashes, please first go to the "Application Info" screen in Settings, and make sure this app have its required-to-work permissions enabled. For example, Browser app need "Storage" if you need to download from it.
[Source / Credits]
- Google / CyanogenMod / Dmitry Grinberg for his awesome work on N4 / Benzo for his nice gapps
[Changelog]
- Check CM changelog related to the date of my build : http://www.cmxlog.com/13/mako
If you find this useful, feel free to hit thanks button, or share it with people you love
.
yeay cm13!!!
Nice! CM13
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
I can't believe this! I haven't tried this myself but this looks extremely promising I'll give this a go!
Wow ,,,,, life doesnt gets any better , wake up and see cm13 for ur device ,,, thx dude
giving this a go !
will post ifi find any bugs ,,, later on
again great work n salute @stephanmc
(19th Oct. 2015): CM13 source code is out. Unofficial ports should be coming in hot now.
n Got that !!
Wowzers
:good: I am amazed
respect
*edit, flashed as soon as I finished work.
gapps_PICO-M-291015-mustbe_txuki_mako instead of Banks. early days, no issues from 1st boot
ahhhhhhh CM feels like home
Is theme chooser included?
mastero9017 said:
Is theme chooser included?
Click to expand...
Click to collapse
I don't think the theme engine works yet cos I tried installing my themes and it wouldn't let me
For those coming from CM12.1 and having flashed CM13: do you see significant battery improvement?
djsubterrain said:
I don't think the theme engine works yet cos I tried installing my themes and it wouldn't let me
Click to expand...
Click to collapse
gave you a thanks coz i'm itching for your 1000th. hahahahaha
i faced problems in this build,was not able to hear anything on call, and whenever phone rings , phone restarts....
gaj05 said:
i faced problems in this build,was not able to hear anything on call, and whenever phone rings , phone restarts....
Click to expand...
Click to collapse
Well, It's a very early build, I don't think CM13 will become daily ROM until december
Sent from my Nexus 4 using XDA Forums
I am quite excited about this build.
But at this point, bug reporting isn't very helpful I guess.
Still, I will give current feedback.
1) download manager seems to crash alot. Or at least the browser being asked to download crashes. Dolphin has its own downloader and does not crash.
2) Chrome (Final or beta) crashes... But It's odd because you get the prompt that it is forced closed but it stays working, and works ok after clicking ok. But the prompt happens often so it is not comfortable to use.
3) sometimes auto screen off, like when reading something and the screen times out, can be very slow to reactivate the device. First time, I thought I had to force restart. Phone completely stops responding for a long time. But only sometimes.
I guess it would be more helpful if I provided a cat log but I only remember that I did not install an app for it yet. I can provide in future if you need.
Sent from my Nexus 4 using Tapatalk
@stephanmc did you make any changes in the source before compiling ? Im having some framework/overlay errors when trying to make my own build but don't know if its the problem in the source or my build environment because I'm building on OSX El Capitan.
drakenabarion said:
I am quite excited about this build.
But at this point, bug reporting isn't very helpful I guess.
Still, I will give current feedback.
1) download manager seems to crash alot. Or at least the browser being asked to download crashes. Dolphin has its own downloader and does not crash.
2) Chrome (Final or beta) crashes... But It's odd because you get the prompt that it is forced closed but it stays working, and works ok after clicking ok. But the prompt happens often so it is not comfortable to use.
3) sometimes auto screen off, like when reading something and the screen times out, can be very slow to reactivate the device. First time, I thought I had to force restart. Phone completely stops responding for a long time. But only sometimes.
I guess it would be more helpful if I provided a cat log but I only remember that I did not install an app for it yet. I can provide in future if you need.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thank you for your report.
"1) download manager seems to crash alot. Or at least the browser being asked to download crashes. Dolphin has its own downloader and does not crash. ".
=> It works if you enable "Storage" permission in Browser Apps info in Settings. Many not-updated apps could crash if they not handle well the new Marshmallow permission system
"2) Chrome (Final or beta) crashes... But It's odd because you get the prompt that it is forced closed but it stays working, and works ok after clicking ok. But the prompt happens often so it is not comfortable to use. "
=> Fixed in latest release 2015-10-31
"3) sometimes auto screen off, like when reading something and the screen times out, can be very slow to reactivate the device. First time, I thought I had to force restart. Phone completely stops responding for a long time. But only sometimes. "
=> Haven't experimented this, but maybe your problem is fixed in latest release
Packsman said:
@stephanmc did you make any changes in the source before compiling ? Im having some framework/overlay errors when trying to make my own build but don't know if its the problem in the source or my build environment because I'm building on OSX El Capitan.
Click to expand...
Click to collapse
It is probably not releated to your build environment, the current CM source tree is actually pretty unstable. Then yes I made some modifications to source to fix build, let me know if you need some help I'll try to find a free time and help you
Some updates for you guys:
- Build 2015-10-31 is out, with nice CM features (Themes works in this build)
- Since October 28, SetupWizard (the first screen which welcome you the first time you install the ROM) was buggy and audio is just broken in CM Source. That's why I planned to fix it instead of making out a build with "no sound" in the phone ^^. I finally fixed that issue of no audio.
- SetupWizard actually freeze at first time. I will look into it in next days when I will have more free time if it is not yet fixed by CM.
- So again about SetupWizard, when you finish install and the phone has booted, just let the phone freeze, then it will auto-reboot, then freeze again, then autoreboot again, then all will become normal
stephanmc said:
It is probably not releated to your build environment, the current CM source tree is actually pretty unstable. Then yes I made some modifications to source to fix build, let me know if you need some help I'll try to find a free time and help you
Click to expand...
Click to collapse
Thank you, I would like to know which modifications u made so I can apply it on my own source, whenever you have time, I would appreciate it very much.
Currently running BlissPop, looking to try a 6.0 ROM. How has this been treating everyone? Does this have theme capabilities, can I use a CM12 theme?
Related
// XT925
// Android 4.2.2
// Current Version [ 4.2.7 ]
// All Languages
{
"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"
}
MIUI ROM 4.2.7 Full Changelog
[Lock screen, Status bar, and Notification shade]
New - Added the option to customize carrier name (Settings-Notifications-Additional settings-Edit service provider name)
Optimization - Improved pulldown notification shade and displayed some information in the status bar
[Weather]
Fix - Location issues of places outside China
[Security Center]
Fix - Display error of phone internal storage in Cleaner
Click to expand...
Click to collapse
MIUIv5 4.2.7 Download
2-14-2014: MIUI v5 4.2.7
Working:
- Everything
* Make sure to enable ADB debugging if you encounter MTP issues.
MIUI General FAQ
Q: How do I root this?
A: Enable root in the perm manager, which can be found in the security folder.
Q: Why is G-Apps not listed for Download?
A: Too Bloaty, add a Google account and install the play store as an APK, I suggest using Aptoide to find it.
Q: 4G LTE isn't working
A: Load the Phone, dial *#*#4636#*#*, goto Phone information, Set preferred network type to LTE/CDMA auto (PRL).
Q: Help! Phone/SystemUI/Keyboard Isn't working/Is Force Closing!
A: Make sure to do a completely clean wipe, also I'm not sure how well this will work if flashed in CWM.
Q: The Browser looks terrible.
A: Settings -> Advanced -> User agent string -> MiOne (It Renders much better & more naturally!)
Q: My Filesystems won't mount/My PC can't see my device/My phone won't act as a MTP/USB Mounting isn't working!
A: Settings -> Developer Options -> Enable Development / USB Debugging (switch both to on)
Misc. Notes
No need to flash any kernels or do any witchcraft, everything should be fine
Tquetski said:
Misc. Notes
Well, this is highly experimental and may require Kernel modding, It may not boot, or it may boot with full functionality.
PLEASE Give feedback even if it is stable[/B ]and I'll do my best to get this in working order If It's broken, but I followed procedure so it should def. not cause any hard bricks.
Click to expand...
Click to collapse
I've always wanted to try it, but just curious: isn't MIUI on V4 now? Have they updated MIUI for 4.2 yet?
You took the Epinter rom as base? it is CM10? So the camera work?
UserDemos said:
I've always wanted to try it, but just curious: isn't MIUI on V4 now? Have they updated MIUI for 4.2 yet?
Click to expand...
Click to collapse
This is MIUI V4, but the build number they are most recent with is 3.11, although I'm using 3.8 as a base for compatibility purposes.
Really, MIUI V4 spans from 2.6 - 3.x.xx I believe
Camera should work, and Yeah It's based on Epinters CM10, I don't know if MIUI has 4.2 support yet- keep me updated on the working order of this rom because there have been 7 DLs but nobody has said that it isn't functioning...so...
So many force closes...
unfortunately android.phone has stopped
Themes
MiuiHome
And have no NAVIGATION BAR
evandro.oliveira said:
So many force closes...
unfortunately android.phone has stopped
Themes
MiuiHome
And have no NAVIGATION BAR
Click to expand...
Click to collapse
Baddabing, I know what the cause of these issues are, they are actually not too hard to resolve and do stem from the same thing. the fact that I got this close means I'll probably have this rom functional much sooner than I thought.
For now I will pull the link to this build while the next build is pending, thank you for the feedback!
Ok, new build is up.
Pretty sure I engaged in too much bull**** with merging and code changes last time to cause the android.phone Force Quit.
Home and Themes FC were a Shelld related issues which now should be resolved.
Edit: Keep in mind a lot of MIUI porting is trial and error, great patience will be needed for a perfect port of this, because of the nature of this one build could fix one thing but break others.
The best way to get a stable port of MIUI is to do everything right the first time, so I'll be trying different things in order to find that golden place of stability.
Thanks again to the folks willing to give feedback, It is more important than any of the things I do in any project.
Tquetski,
i still have issues with android.phone on v2, several force closes.
Is it home, launcher? The way you respond will help me determine if I really have to edit your kernel which is starting to feel like an inevitability lol :l
Guys, I'm going to bump this to ask if in the builds I posted, did the status bar appear in any of them?
As soon as this single bad issue is resolved I will be able to bring a fully functional MIUI to this device, I've already created a kernel for this device to be used exclusively with MIUI roms, but before I make the next test build, did the second fix the status bar?
The next build will include the kernel either way, but if this one is fine outside of needing the kernel I see no reason to re-port : P
Again, ALL FORCE QUITS ARE KERNEL RELATED and not indicative of progress If you do not have a MIUI kernel, all I need for people to watch for is a working status bar It appears midway through rom setup, it does not initially appear right away, so I'd appreciate it if folks would wait to get to the MIUI launcher before commenting on if the bar may or may not be missing
The status bar is visible for me. I installed 0.2 Alpha.
Also none of the on-screen buttons work. I'm not sure if this is related to the force closes, but thought I'd mention it just in case.
Ok! New build is up, as with the other two builds I have also re-ported this from the ground up.
Fixes SHOULD include all phone lights, Force Quits in Home and Themes have been fully resolved.
This Rom includes a MIUI specific Kernel as well
Edit: Now that I've taken the effort to make a Kernel for this rom It is only a matter of time before It's fully functional, If you were to use this kernel in 0.2 of this rom it would resolve all FC issues relating to home launcher and other system components.
I felt the need to ground-up it due to the LED light framework error, which should be fixed here but I can't be positive,I need full bug reports asap : )
constant reboot during power up. wont even reach logo. tried to wipe everything 2 times but still not working.
Krizid said:
constant reboot during power up. wont even reach logo. tried to wipe everything 2 times but still not working.
Click to expand...
Click to collapse
Frontal keys are a *****, Krizid is testing before I post a release, the next forum post will likely be a functional rom, stay tuned : )
Progress Report
MIUI is currently fully functional
MIUI currently needs a kernel. If anyone here can unpack and repack this phones boot.img without causing a bootloop
contact me asap, a kernel or way to run shelld is all that is left
So either
1) MIUI Kernel to call Shelld
2) Some other means of calling shelld
Let me know if anyone has ideas!
Progress Report
2/26/13
Broken
- Unable to hang up calls
- System UI Force Quit upon editing Navbar properties
(Not a big deal, just annoying)
MIUI Kernel has been completed, It's possible I may be able to post a build tonite or tomorrow.
OK folks, I'm posting a build of this for observation purposes and also for the kernel, in case other people want to help debug this, or make their own MIUI to speed up the time this phone can have a fully functional MIUI : D
Once again, this is an alpha that does mostly work, but is broken in places that really need fixing, I will post another build when this enters beta
Tquetski said:
OK folks, I'm posting a build of this for observation purposes and also for the kernel, in case other people want to help debug this, or make their own MIUI to speed up the time this phone can have a fully functional MIUI : D
Once again, this is an alpha that does mostly work, but is broken in places that really need fixing, I will post another build when this enters beta
Click to expand...
Click to collapse
What's MIUI based on? CM10? Just curious...
Isn't MIUI V5 due out March 1st? Will you be able to to simply add merge code like CM does currently for future releases?
Also, as someone hesitant to switch to anything other than stock (which is so functional)...how does MIUI incorporate Google Apps?
°°°
Attention: This ROM is discontinued!
It still works great as a daily driver and got a large userbase, but as CM10.1 has been abandoned there won't come any new updates anymore!
After working really hard on it for more than 2 month(!) I proudly present my first CM10.1 T-Build :fingers-crossed:
I put lots and lots of effort into it to create a great, smooth and bugfree rom experience for you guys.
I tried to fix all huge bugs on CM10.1 like bluetooth fast forwarding and the wifi hotspot.
Additionally I took the time to create a non-neon gapps package, as the official 4.2 one does only support neon.
{
"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"
}
If you appreciate all the effort that has gone into this ROM then consider a donation.
While it's neither expected nor required it is highly appreciated!
> Paypal Donate link <
Each donator will get a huge thank you and a private dance show
Preview (you can't wait for the leafs getting down now, can you!):
(and as I've been asked a couple times in the past: yes, you can send me an amazon gift card code via PM as wel!)
CM Known Bugs & Fixes:
This list shows what has been done so far.
As you can guess by the sheer amount of the fixed bugs there has been put lots and lots of time into this ROM.
And don't forget about all the awesome work pengus77 has put into the kernel - without him we would still suffer from bsods and huge battery drain.
Do NOT post or ask about stuff on the known bugs list!
The bug is listed here - I don't need to get reminded that it's there.
If there's progress or an ETA or anything we will post about it - if not there's not.
I really mean it! Do not ask, it's just annoying. It might only lead to us abandoning the work on the bug.
Oh check the "plans for the next build" section below as well.
But of course you're very welcome to post a decent fixing idea or development related note in'te the CM10.1 development discussion.
Hall of shame of people who ignored my warnings and still posted about already known bugs.
If someone continuously breaks this threads rules you'll land on my ignore list.
tonyp (damn!)
CM10.1 specific bugs:
Bluetooth is accellerating on many headsets fixed (by replacing the bdroid bt stack with bluez)
Wifi hotspot isn't working fixed (by forwardporting the CM10 internal hotspot handling to CM10.1)
SDCard write speed is subpar. not fixed
bugs affecting all CM10+ based ROMs (unordered list):
unable to reject calls on SU660 basebands fixed
low brightness after unlocking fixed
automatic time on SU660 and v30x basebands is broken fixed
wifi & 3g drain fixed (Kowalski Kernel)
notification lights aren't working fixed
zram is selected at 18% but isn't enabled fixed
init..rc contains some parameters interfering with the kernel configs fixed
bootanimation gets displayed "too long" fixed
CM10.1 Performance CPU settings aren't compatible with our Tegra CPU fixed
you can't bind the searchkey to actions like opening the recent app drawer fixed
FM radio isn't working fixed (see here)
In-Call muting fixed
Call forwarding fixed
autobrightness isn't working properly semi-fixed (kk120+ - kernel instead of ROM controlled, so you can't control it in the ROM, but via a sysfs)
Stock camera has some drawbacks (especially panorama & hdr) semi-fixed (by his or this ported LG Stock camera)
HDMI isn't usable not fixed
no signal after airplane mode bug (double press data or reboot to gain it back) not fixed
Changes and cherrypicks to the CM10.1 codebase:
Major Changes:
The codebase is CM10.1.0 RC4
fixed all the bugs above
incuded tiny non-neon gapps
Development settings enabled by default
Advanced reboot enabled by default
tonyp memory management added and enabled by default
(you can turn it off at Settings - Performance - Memory management)
purgeable assets enabled by default
enabled Pie Controls
Vibrations lowered (no, you can't change it back easily)
removed the autobrightness configuration options
(it's kernel controlled, you can't change it in the ROM!)
removed Videoeditor (and some LWPs)
added the awesome epic Kowalski kernel as prebuilt
(including KowalskiManager, alsa mixer and tx power stuff)
added a ****ing epic easteregg
Cherrypicks:
added more options to rebind the hardwarekey
added more options to the lockscreen longpress buttons
(including screen off! save the power power button some presses!)
option to pull down the Quick Settings panel when there are no new notifications
added a notification drawer brightness slider
option to disable the CRT animation
Center Clock option
Text-only batterystyle
Quickmemo framework support
Option to disable the lockscreen Camera widget
Custom carrier text
Recents RAM bar
much much more - read the changelogs linked at the end of the next post
Plans for future builds:
Bugs fixes:
-
Other:
GCC 4.7 experiments
CREDITS:
arcee and the CM team for all the work they did.
pengus77 for his awesome work at the kernel and new bootloader.
niko (Andrei E.) for his work on including the bluez stack into android.
marsgod for fixing the callbug on the old bootloader.
wkpark for the cracked ICS bootloader, the ramhack idea, and all is valid input.
goo.im, AndroidFileHost and vadonka for providing me great hosting services.
I got a bug - can I report it?:
If you want me to take the time to help and fix your bugs I expect you to take the time and do this properly!
Quick check: Did you do a full wipe before installing build 01? If not you need to do that first!
Check the known bugs section. If it's listed or mentioned there, drop it (and wait patiently if it'll get fixed eventually).
Use the search function and try to find if others have been posted about it.
You're only at the app and can't properly search within a thread?
Then wait until you're at home and report the bug from there!
Check the last 3 pages if the bug has been mentioned there.
You still with me? All of this takes too much of your precious time?
Then use another ROM!
Still nothing? Then report the bug in this thread.
Always attach logs to your bugreport!! Bug reports without logs will get ignored completely.
Study this for more details: [Reference] How to get useful logs
People who fail in doing this properly will get into the hall of shame.
Downloads:
ROM:
By downloading and/or using this ROM you agree to the guidlines of this thread:
Read and understand the entire OP!
Yes, it takes a couple minutes - but what's that compared to the 2+ month I put into the ROM??
Don't be a douchebag!
Follow the rules!
If you agree click the button and download the ROM :fingers-crossed:
Download: http://tonyp.basketbuild.com
Make sure to download the correct version for your bootloader!
Mirror: http://goo.im/devs/tonyp
Gapps:
This ROM already has tiny gapps included! That's a minimum gapps package (<20mb)
I put a lot of effort into integrating the required apps and libs and tested it carefully.
I choose this approach because of the many problems that the standard package causes to our non-neon Tegra2 phone.
Included are only the most basic (g)apps like Playstore, Talk (with working videochat), Calendar sync provicer etc.
If you want to remove the included gapps flash this package after flashing the ROM:
CM10.1-gapps-remover-tonyp.zip
For those of you who want the "full" gapps package including Google Now, TTS, Faceunlock, voice search etc. I worked on a full non-neon gapps package.
Get it from this thread: Non-neon Gapps (Android 4.2) dev-discussion thread
Do NOT flash any other gapps package - they aren't compatible with our phone!
If you accidently did that then format /system and reflash the ROM.
This is necessary to prevent bugs like like the keyboard closing while typing.
Addons:
You can download my officially supported addons from the addons folder:
http://goo.im/devs/tonyp/CM10.1-T-Builds/addons
This ROM has native support for Quickmemo.
For more details read this post.
I've build patches for OpenPdroid and PDroid2.0.
For more details read this post.
Kernel:
kowalski kernel thread
This ROM comes with the awesome kowalski kernel by pengus77.
For new versions (which come regularly) check out his thread!
Various:
TWRP recovery for both bootloaders
my modded adb drivers
Instructions:
Updating to a newer T-Build::
No wipes or system-format needed!
Choose the correct ROM for your bootloader
Flash the ROM
Flash the latest kowalski kernel
Tiny Gapps are included, so there's no need to flash gapps if those are enough for you.
If you want the full gapps package use the non-neon one I provide here.
If you want to remove gapps flash this package after flashing the ROM: CM10.1-gapps-remover-tonyp.zip
Reboot
Coming from another ROM:
If you're on the newbl either use pengus CWM 6.0.2.5 or my TWRP!
Other recoveries won't work.
oldbl users can use any CWM >5 or TWRP version.
Do a full wipe!
Just do the wipe, you will be thankful afterwards when everything does run better.
Format /system
Choose the correct ROM for your bootloader
Flash the ROM
Flash the latest kowalski kernel
Tiny Gapps are included, so there's no need to flash gapps if those are enough for you.
If you want the full gapps package use the non-neon one I provide here.
If you want to remove gapps flash this package after flashing the ROM: CM10.1-gapps-remover-tonyp.zip
Reboot
Don't restore system apps (like Settings) or system data (like Wifi data) with TitaniumBackup!
My personal recommended configuration:
Go to Settings - Performance - Processor and change the "Maximum CPU frequency" to 1200 (or even 1500) and "Set on Boot"
Open the KowalskiManager
enable the 3 power saving options at the top
lower TX Power to 11
Change the SD readaheads to 512
enable dynamic fsync
This ROM comes pre-configured with the following memory management changes:
zRAM enabled with 18%
tonyp memory management enabled
purgeable assets enabled
Changelog:
T-Build 01
T-Build 02
T-Build 03
T-Build 04
T-Build 05
Let me leave with a couple more notes:
This ROMs focus is stability! It's intention is to be a daily driver without the need to constantly flash new updates - that's why I kept you guys waiting that long and didn't release my daily testbuilds (more like 3 builds a day actually) which haven't been perfectly stable, yet.
That's why I took CM10.1 M3 as a base and don't merge in nightly features - everything in this ROM should be well tested and fully working.
I only picked memoryleak fix that's been discovered after M3.
I won't cherrypick each and every feature that's in some other ROM!
If there's a real useful addition that I personally like I will do it, but the fancy stuff has to go into other ROMs.
You guys know me - I am mostly patient and don't mind slight offtopic posts.
For completely offtopic posts you can use the CM 10.1 discussion thread.
... but I hate people who are lazy and don't do their own research. I spent countless hours on this ROM, I think I can expect you to spent a little time before asking questions.
I am not a vendor who's obligated to release a ROM for the phone - I am doing this in my free time for you and me.
So please - don't behave like a total noob. Or [email protected] and I will have a busy fishlapping time
F.A.Q. - Frequently Asked Questions:
How can I swap the mounting points for internal SD card and external SD card?
If you're on the new bootloader, flash this script via Recovery (thanks, @C0D3N1N3R!). For those on the old bootloader, you need this one instead (thanks, @SWTR!).
Which gapps package should I use with this ROM?
Seriously? You haven't been paying attention, have you? Go read the posts above this one!
Which PDroid version should I use?
It's a matter of personal preference, actually. Try both and see which one fits your needs the best. Keep in mind that if you're switching between Openpdroid and PDroid 2.0 (or viceversa) you need to uninstall the app and re-flash the ROM first, or else this kitten will die and it'll be in your conscience forever! I'm serious!!
Just flashed this ROM via recovery and can't get past the boot logo, what's wrong?
Chances are that you're using the wrong Recovery. Try pengus' CMW v6.0.2.5 and flash the ROM again. If the problem persists, check that the ROM zip file isn't corrupted (see each build's md5 hash on tonyp's goo.im CM10.1 folder). If none of that helps, then you better get Tony some logs
How can I know which bootloader my device is using?
An easy way to indentify this is by seeing the bootloader logo that appears when you turn on your device: white -> old bootloader, pink -> new bootloader.
How can I set a custom DPI on this ROM?
You can either use the Google Play DPI Fix Tool, or Tony's personal recommendation: Xposed in combination with Xposed App Settings (link down, use this one or this one instead for now) (see reference by @rugglez).
Viber doesn't work on this ROM, I can't even make a call. What can I do?
According to what we have read, recent versions of Viber won't work on CM 10+ for our device. Apparently, the developers of the app were been notified about the issue and they might look into it soon. Worry not, my friend, since not everything is lost. According to @engine24, Viber version 2.3.6.338 seems to be working alright. Make sure you uninstall your current version of Viber first before installing this one, though!
Battery drain is a bit too high, what's happening?
If you just flashed this ROM, please do one or two full battery charge cycles and see if it helps. Also, check on BetterBatteryStats for rogue apps keeping your device awake (and this is definitely worth a read!).
My screen goes bright before unlocking / after locking?
It's a known issue when using autobrightness. There's no fix for this at the moment.
My GPS takes ages to get a lock, how can I fix it?
Try the latest version available of the Google Specific No-SSL AGPS patch by @crypted. Unpack the gps.conf file and copy it into /system/etc/ using a root file explorer (set permissions to rw-r--r--). Optionally, you can add ro.ril.def.agps.mode = 1 to build.prop (find it in /system folder) but only if you're still having problems after applying the patch.
And, in case you're wondering, the answer is no: this patch won't be integrated into the ROM, so don't ask ... or will it?
Edit: that damn Tony added it to T-Build 3, so this is no longer necessary (unless he decides to drop it hehe)
Hardware Search key is not working!
Go to Settings > System > Hardware keys and make sure that Enable custom actions is checked. Also, change Search key action to In-app Search.
Spoiler post
Well the title says it all
Spoiler nr1. here is a screenshot of battery life with this rom and KK121...
Yeah im already curious...........tout de meilleur frère :laugh:
Waiting for upload to finish....merci
rmrajm1 said:
Yeah im already curious...........tout de meilleur frère :laugh:
Waiting for upload to finish....merci
Click to expand...
Click to collapse
Already finished, tony has great upload speed hehe
Loving the structure and text of the thread, though, same with the pictures
Sent from my LG-P990 using xda premium
Can:t w8!! Good job guys!!
Sent from my LG-P990 using xda premium
Oleeeeee
Gesendet von meinem LG-P990 mit Tapatalk 2
Thanks alot , well done .. will be testing it in moments
Congrats for the release tonyp. I've been with your test builds since I found them so I'm waiting eagerly to try this final build.
Thanks for the great work!
great job done.....I am thrilled to try a CM ROM....will report a feedback....
I am sure it will rock
CONGRATS and THANKS for the hard work.
Congrats downloading it
Sent from my LG-P990 using xda premium
This sounds great. Thank you for the sacrifices you've made a big investment in this old phone that can still be done to compete with the newer devices.:thumbup::beer:
Sent from my LG-P990 using Tapatalk 2
tonyp congratulations.
Thanks for your hard work
Sent from my LG-P990 using xda app-developers app
Yeah... downloading... :victory:
I found the easter egg.. :laugh::good:
Subscribed and ready for fishslapping... xD
Downloading and flashing too.
Thank you tonyp!
Hey there! I'm just a builder who want to share with all of you the compiled sources of Paranoid (Credits to the team for all the work and gerrit patches I've used).
It's an alpha, so it doesn't have many features:
- It has an advanced power menu with options to reboot (recovery, bootloader, reboot), screenshots, etc.
- Head-up notifications have been improve (using Hover sources I guess)
- Ambient Display has been added for our device too (replacing peek at this moment)
- Quick unlock is enabled.
- Quicksettings' tiles reorder
- Inmersion mode with tile support
- OnTheSpot is now implemented, but there isn't any example of it.
- ParanoidOTA comes with the rom, but isn't functional right now.
- Another smalls changes and improvements.
- CM12 Theme Engine
- Linked volumes and expandable volume panel
- Added a standalone File Manager
If you want to check all the new stuff of every build please visit gerrit. It works fine with TWRP and also multirom.
All the builds like build 4 or newer, will be compile from sources, without adding any feature, so they will be clean builds. I will try to get new ones every month until the team release their own ones, so enjoy them, and if you like my work, click Thanks #StayParanoid
Links
ROM(build 5): https://goo.gl/AvVlwz
GERRIT(changelog): http://goo.gl/wZamJf
GAPPS: http://goo.gl/kNcpB7
ROOT:http://goo.gl/DUhWyI
Installation
- Download the rom, the gapps you prefer and the root zip.
- Do a factory wipe in recovery (if you are updating from a previus paranoid 5.1 build just wipe dalvik&cache).
- Flash the three zips in the same order as above.
- Reboot and enjoy the rom!
Old Builds
Build 1 (11/01): http://goo.gl/kRMTBV
Build 2 (18/01): http://goo.gl/Xd6XXS
Build 3 (1/02): http://goo.gl/kLx10r
Build 4 (26/05): https://goo.gl/eaZg0O
Screenshots
{
"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"
}
One of my favorite ROMs since I moved to Android! Flashing for sure later! Moving to this ASAP xD
Sent from my Nexus 4 using XDA Free mobile app
damn, wont flash with twrp 2.8.3.2 ....
DJ_Uro_UE said:
damn, wont flash with twrp 2.8.3.2 ....
Click to expand...
Click to collapse
What's the problem?
Thanks bud!
Wooohooooo!!! It's finally coming!! :cyclops: Thanks for the build
many many MANY bugs with this...rotation does not work...even messes with rotation apps. Reboot menu only has reboot...no recovery or bootloader option. LTE 100% does not work...switch it on and loose data altogether. Rom will not flash in TWRP 2840...something about symlinks.
That's all I found before I got fed up and restored my factory backup. Seriously, thank you for taking the time to build and share this...I'm appreciative of that, believe me. This is just as far from usable for a daily rom as I've seen in a long time is all.
hp420 said:
many many MANY bugs with this...rotation does not work...even messes with rotation apps. Reboot menu only has reboot...no recovery or bootloader option. LTE 100% does not work...switch it on and loose data altogether. Rom will not flash in TWRP 2840...something about symlinks.
That's all I found before I got fed up and restored my factory backup. Seriously, thank you for taking the time to build and share this...I'm appreciative of that, believe me. This is just as far from usable for a daily rom as I've seen in a long time is all.
Click to expand...
Click to collapse
It's a shame that it has all this problems, but you have to remind that this is an alpha version , and for example you can find in gerrit patches for LTE that are in state of review, so if you want I can cherrypick them in next build.
About the powermenu options, you have to enable developer-settings, and there you will find an option to enable advanced reboot menu.
Finally with the build I will compile this saturday I will see what de can do to avoid the errors with the recovery, and also I will check the rotation.
yaymalaga said:
It's a shame that it has all this problems, but you have to remind that this is an alpha version , and for example you can find in gerrit patches for LTE that are in state of review, so if you want I can cherrypick them in next build.
About the powermenu options, you have to enable developer-settings, and there you will find an option to enable advanced reboot menu.
Finally with the build I will compile this saturday I will see what de can do to avoid the errors with the recovery, and also I will check the rotation.
Click to expand...
Click to collapse
Thank you. I totally understand it's a first build in early stages. I wasn't trying to beat you up...the problems could be in the source. I just wanted to let everyone know this shouldn't be expected to be a daily just yet, so they don't go in with high hopes and have them killed when all these things start going wrong. There are some builds that are definitely suitable as daily drivers as first-draft alpha builds, so it wouldn't be that surprising to find this one to be one of them, but unfortunately it's just not.
hp420 said:
Thank you. I totally understand it's a first build in early stages. I wasn't trying to beat you up...the problems could be in the source. I just wanted to let everyone know this shouldn't be expected to be a daily just yet, so they don't go in with high hopes and have them killed when all these things start going wrong. There are some builds that are definitely suitable as daily drivers as first-draft alpha builds, so it wouldn't be that surprising to find this one to be one of them, but unfortunately it's just not.
Click to expand...
Click to collapse
I must say that i'm running it without any problems at all.
Flashed successfully using TWRP.
Rotation is working fine.
So I would say go go go to all hesitating to update....
Thulin said:
I must say that i'm running it without any problems at all.
Flashed successfully using TWRP.
Rotation is working fine.
So I would say go go go to all hesitating to update....
Click to expand...
Click to collapse
Can you give us some screenshots please
Thulin said:
I must say that i'm running it without any problems at all.
Flashed successfully using TWRP.
Rotation is working fine.
So I would say go go go to all hesitating to update....
Click to expand...
Click to collapse
That's good to hear...would you please tell us what version of twrp you used? I tried 2840 and got the symlink error. I reverted back to 2820 since that's the newest I had stored on my pc and it flashed.....but with all these bugs I listed. Maybe it's not flashing properly still???
I had native rotation on and it didn't wok, so I downloaded Ultimate Rotation Control ( https://play.google.com/store/apps/details?id=nl.fameit.rotate&hl=en ) which works fine for me on 5.0.1 factory image....it was missing several rotation options with this rom, and the only option that worked was manual, which consists of a notification widget and clicking the angle of rotation you want, in order to change it....and it locks to that position. Like I said, maybe it messed up flashing...it definitely had some real issues. I'll try again and report back
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
SebiC98 said:
Can you give us some screenshots please
Click to expand...
Click to collapse
It's nearly 100% stock AOSP, from the looks of it. It doesn't have any options besides the reboot menu, that I know of.
SebiC98 said:
Can you give us some screenshots please
Click to expand...
Click to collapse
Sceenshots of what, it's pretty much just stock lollipop at the moment. Nothing to show off....
TWRP: 2.8.3.0 was used.....
any one try it in multirom??
is it work??
qzxi said:
any one try it in multirom??
is it work??
Click to expand...
Click to collapse
Yep, I use it to test the builds
Build 2 is up, see gerrit for changes!
yaymalaga said:
Build 2 is up, see gerrit for changes!
Click to expand...
Click to collapse
How's the performance of this? Does it still have the launcher redraws due to memory leak?
Cool, I'm still waiting for some new stuff from PA
Thanks mate That´s what i was waiting for
jer_ying_fd said:
How's the performance of this? Does it still have the launcher redraws due to memory leak?
Click to expand...
Click to collapse
It's almost the same as a clean aosp rom. They have fixed memory leaks, but I don't remeber anyone about the launcher.
As Cyanogen pulled the plug on CyanogenMod, this project will continue under Lineage OS
{
"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"
}
This ROM is Alpha and not ready for daily use at the moment
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@RaymanFX
@CTXz
I used @RaymanFX's T815 image to base my cm 13.0 build on, which in turn is the base of this cm-14.1.
Before you start
THIS ROM IS ONLY FOR THE SM-T810
Code:
*
* Your warranty will be voided !
*
* 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.
*
About the ROM
Current state of ROM : testing
Everything except what's reported below is working (or not yet reported as not working).
What is Fixed
In '20-09' build reboot to recovery triggers message 'Factory reset'. (wrong messagem not resetting)
Camera not working in selinux enforcing
Front facing camera unable to save image
Bluetooth not working
Hardware codecs not working (fallback to software for mp3/flac works)
Limited wifi 5GHz support (channels above 100 give issues)
Video recording not working? (not tested on T810, reported not working on T815)
What is not working
Important
Fingerprint scanner not working
Minor
Compass is 180 degrees mis-aligned
Mic not working (no input routing)
Instructions
How to install CM13.0
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 14.1 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
08-12-2016 - Compile with curren cm-14.1 source and [URL="https://review.cyanogenmod.org/#/c/173951"]this patch[/URL].
**********
25-11-2016 - Cm-14.0 is abandoned upstream, limiting uploads to cm-14.1.
- Recompile with camera fix merged in cm sources.
**********
21-11-2016 - Fixed camera (again).
**********
20-11-2016 - Broke camera in enforcing mode (unable to save picture).
**********
17-11-2016 - Recompile from clean tree, camera and youtube work now.
- Confirmed lock-screen-rotate fixed, but only after clean flash and [b]no restore of device ID[/b].
**********
14-11-2016 - First succesful cm-14.1 boot. (Switched project to cm-14.x)
**********
31-10-2016 - Selinux set to enforcing.
**********
12-10-2016 - Disabled telephony that got included regardless specifying I don't want it.
- Fixed several bluetooth issues
- Removed use of old api (v1) by camera
**********
03-10-2016 - First build with cm-14.0 release (previous were staging builds)
- Fixed bluetooth
**********
25-09-2016 - Fixed selinux contexts for camera so it works in enforcing mode
- Fixed front facing camera so it is able to save images.
**********
22-09-2016 - Reboot to recovery now triggers correct message
- 2nd build selinux permissive.
**********
20-09-2016 - 1st cm-14.0 build
**********
Downloads
Latest CM 14.1 build : https://www.androidfilehost.com/?fid=673368273298915423
All CM 14.1 releases can be found here : https://www.androidfilehost.com/?w=files&flid=128488
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, and already patching the common sources to cm-14.0, without him this ROM would most likely not be possible!
All my sources can be found here : https://github.com/CyanogenMod/android_device_samsung_gts210wifi
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
CyanogenMod 14.1 for Tab S2 9.7 wifi, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, Raymanfx, CTXz
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: Cyanogenmod
Version Information
Status: Alpha
Created 2016-09-22
Last Updated 2016-12-29
Nice! Thank your very much for this early build!
I will try it as soon as I am able.
Sent from my SM-T810 using XDA-Developers mobile app
GO hard brother, thanks for all your efforts!
I've been using cm-14 since the 20-9 build, it's running pretty stable, although it's even more stable with selinux in permissive. Looks like some contexts have changed a bit in cm-14. (or the camera and some other routines ignore them)
I found 1 game not playing nicely with Nougat, CSR Classics, but the racing set from CSR work nicely, so I think that's a CSR related bug.
Fixed camera so it'll work in selinux enforcing (not yet activated) and front facing camera is able to save images.
Updated OP.
Awesome thank you!
@T_I Thought you might like 2 comments re your really great adaptation of CM14. Have been using your CM13 nightly downloads for about the last 5 weeks on my T810 and was so pleased with the result that I was slightly hesitant about trying CM14, however this afternoon I took the plunge and installed it as per your instructions. First impression is that I can hardly believe how problem free the installation of the Rom and the Open Gapps 7.0 pico proved to be.
I don't have a huge number of apps installed, about 30, but with one exception they are all performing as scheduled and I couldn't be more pleased, the one app that doesn't work is "Set CPU", there is no "forced closure", no error message, it just doesn't work. There are no forced closures of any other app including the Google Play & Services.
One point which might interest you as you mentioned it in your "OP" notes. I play mp4 movies using the app "MX Player Pro" with the Arm 7 codec installed and they play using the HW+ codec perfectly,
Was initially disappointed that "Theme Chooser" was missing from "Settings" but I can live with that considering how well everything else performs.
Once more congratulations on a really superb "port".
EDIT on 09.27.... @T_I I know this point is insignificant and pure "eye candy" but I love the touch ..... I'm talking about when one connects a usb connection from PC to S2 then the "icon" displayed at top left is now "N" (for Nougat ?) instead of the normal CM icon.
planning to attempt with the t710 again?lol
NalNalas said:
I've had this flashed since last night, and the battery so far has been great. Thanks a ton for this.
Click to expand...
Click to collapse
How much better would you say the battery life has been?
Would also appreciate input from anyone else whos noticed a difference (good or bad) with the battery life.
This ROM is working great so far!!
samsung_xoom said:
planning to attempt with the t710 again?lol
Click to expand...
Click to collapse
I can run a cm-14 build for T710 to see if that one boots.
I can test it and let you know , in my limited time I have lol
This rom is very stable, fast and reliable. The battery life is excelent. I use it as my daily driver since sept. 22!!! (Now i have a sept. 27 update)
Thanks T_I for your hard work!!!
Uploaded new image. @RaymanFX got bluetooth working on his device and the fix works on T810 as well. Also CM switched cm-14.0 from staging to release. There is still work to be done, but build shows working bluetooth (at least I can connect a keyboard and that one works).
I noticed crashing phone app and saw one ExchangeServices crash. (don't use both) Updates OP.
Latest build works wonders after I deleted from /system/app and /system/priv-app all the apks related to telephony/SMS/MMS/etc. for my T810.
EDIT: After some time, it all came crashing down, Play Services didn't like the removal of the packages, and some apps auto-removed themselves. Better wait until dev ships out another build.
Just tried to install the Oct 3 version of this ROM and as soon as it boots a box appears saying "com.android.phone has stopped". No matter how many times I click OK, the message just reappears and I can't get past it. Even have to use the power-home-vol- button combination to power off. This is on a T810 after full wipe, install ROM and install 7pico gapps. Tried the install three times. Coming from cellular south 6 ROM.
Please don't forget T710....
lewmur said:
Just tried to install the Oct 3 version of this ROM and as soon as it boots a box appears saying "com.android.phone has stopped". No matter how many times I click OK, the message just reappears and I can't get past it. Even have to use the power-home-vol- button combination to power off. This is on a T810 after full wipe, install ROM and install 7pico gapps. Tried the install three times. Coming from cellular south 6 ROM.
Click to expand...
Click to collapse
I got the same message, but can mute. Don't know where it comes from. I was working on the staging version of cm-14 and switched to the release version. Looks like there are some bugs left. (it's now less stable then with the staging cm-14)
T_I said:
I got the same message, but can mute. Don't know where it comes from. I was working on the staging version of cm-14 and switched to the release version. Looks like there are some bugs left. (it's now less stable then with the staging cm-14)
Click to expand...
Click to collapse
Just by clicking the OK button? Message just pop right back up when I do that.
lewmur said:
Just by clicking the OK button? Message just pop right back up when I do that.
Click to expand...
Click to collapse
I get the message with the 2 options 'stop application' and 'Mute until reboot'. The Mute option silences the warnings, but the app will still misbehave.
Exchange services I've been able to freeze, the phone app is also used for syncing contacts and I think calendar.
{
"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"
}
Omnirom 4.4.4 FOR MINI2
First i want to thank @TheWhisp for his sources
this is Android Omnirom for s6500 and s6500d
- What not Working
Camcorder
NFC(S6500 only)
- What Working :
Everthing
Install method for s6500d only:
-Download and install CWM 6.0.5.1
-Download the rom
-Download google apps
-Copy the rom and gapps to external storage
-Wipe data,cache,format system
-Install the rom and gapps and the fix
-enjoy
Install method for s6500 only: plz follow the instructions
Im not responsable for any damaged phone so do it on your own risk
-install twrp and reboot in recovery
- go to wipe and Advanced wipe and then wipe cache , system
-in advanced wipe choose data and go to repair or change file system
- go to change file system and choose EXT4
-Install the Rom
-Reboot recovery
-Install gapps
-Enjoy
- Downloads for S6500
Rom V2:https://drive.google.com/file/d/1-A2KadQCyRqxQqSuy_bFeL1ALxPd8t99/view
Gapps :https://androidfilehost.com/?fid=23610159112653717
TWRP 3.0.2.0 Odin : https://drive.google.com/open?id=1TU...v_m0MfaaxWtspr
- Downloads for S6500d
Very Soon
For the S6500 Install Video , this is the Link : https://www.youtube.com/watch?v=ACLEn63Nvi8&feature=youtu.be
Credits :
-TheWhisp
-erikcas
-Konstat For some patches
-Samsung
-bleached for some motivation
-lorn10 "special thanks for you"
if you consider Donating thanks
XDA:DevDB Information
[ROM][3.4] Omnirom 4.4.4 Stable For Mini 2, ROM for the Samsung Galaxy Mini
Contributors
Shadow Of Leaf
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-08-20
Last Updated 2018-08-20
Changelog and Screenshot
Changelog
-V1 20-08-2018 : Initial Version
-V2 04/10/2019 : Fix the call Hang bug (i guess cause sim card slot doesnt recognize my simcard hardware failure so test and report) and some optimisations
***NOTE*** to USE Omnirom 4.4.4 with art and GAPPS you need a supported gapps packages this is a link for gapps working on art http://www.mediafire.com/file/typy3b6nq94r48f/GApps_Light_4.4.x_signed.zip/file
Hello.
First, thank you very much. It is working really fine.
But I have a problem, I can not receive calls. I can make calls, but when someone calls my number, my phone does nothing. It is working with cm11. I've tried several sim cards, from different companies, none worked. I've looked for usual solutions, but no luck.
It is a shame,becasuuse this is working much better tahn cm11. Do you think there is something I can do?
Thanks again.
aficionadodesu said:
Hello.
First, thank you very much. It is working really fine.
But I have a problem, I can not receive calls. I can make calls, but when someone calls my number, my phone does nothing. It is working with cm11. I've tried several sim cards, from different companies, none worked. I've looked for usual solutions, but no luck.
It is a shame,becasuuse this is working much better tahn cm11. Do you think there is something I can do?
Thanks again.
Click to expand...
Click to collapse
Thanks for reporting
It will be fixed soon
And build for s6500d also
Stay tune
so what ? is it working now or not ?
hi , can i use this ROM for GT-S5570i ??
if not, could you please creat one for GT-S5570i
but is update? it's work on s6500
hello this rom support turkish language?
ardakerem said:
hello this rom support turkish language?
Click to expand...
Click to collapse
yes it have all language
This is really AWESOME work Shadow Of Leaf! Many thanks for this great mini 2 Omnirom 4.4.4. :good:
I didn't know that you are still developing for the mini 2. I have discovered this latest KitKat rom just some time ago. It works in almost every regard better then all the previous CM11 builds. It is again somewhat more fluent (speedy) and is out of mine view less laggy when comparing with the previous builds.
However, - as already mentioned there is only one grave issue present. I also don't receive any calls.
I think the problem is located in the mobile network setting or a different mobile network driver. As network type UMTS is showed, - all the previous KitKat builds showed (in my case) HSPA or something else but never UMTS. I tried to enforce "2G/3G Preferred" and "2G/3G Auto" but they wouldn't be accepted. It was possible to set the Network to "3G Only" and "2G Only" but the call receiving still doesen't work.
Furthermore when I make a call and want to hang it up, - I can push the red hang up tab but the call will not be terminated. So the call is still open but it is not visible (at the phone) that the call is still active.
As mentioned in some other threads, - my mini 2 has baseband version S6500XXMD1.
Whatever, - you may fix this in a future update. It would be great if you can include one brighter background file, - the two standard one are quite some dark.
Yes, and yours TWRP 3.0.2.0 works absolutely stable. Much better than the previous TWRP version.
Will send you for all this work a litte donation. Kind regards,
lorn10
lorn10 said:
This is really AWESOME work Shadow Of Leaf! Many thanks for this great mini 2 Omnirom 4.4.4. :good:
I didn't know that you are still developing for the mini 2. I have discovered this latest KitKat rom just some time ago. It works in almost every regard better then all the previous CM11 builds. It is again somewhat more fluent (speedy) and is out of mine view less laggy when comparing with the previous builds.
However, - as already mentioned there is only one grave issue present. I also don't receive any calls.
I think the problem is located in the mobile network setting or a different mobile network driver. As network type UMTS is showed, - all the previous KitKat builds showed (in my case) HSPA or something else but never UMTS. I tried to enforce "2G/3G Preferred" and "2G/3G Auto" but they wouldn't be accepted. It was possible to set the Network to "3G Only" and "2G Only" but the call receiving still doesen't work.
Furthermore when I make a call and want to hang it up, - I can push the red hang up tab but the call will not be terminated. So the call is still open but it is not visible (at the phone) that the call is still active.
As mentioned in some other threads, - my mini 2 has baseband version S6500XXMD1.
Whatever, - you may fix this in a future update. It would be great if you can include one brighter background file, - the two standard one are quite some dark.
Yes, and yours TWRP 3.0.2.0 works absolutely stable. Much better than the previous TWRP version.
Will send you for all this work a litte donation. Kind regards,
lorn10
Click to expand...
Click to collapse
Hello
Thanks for your amazing work
i upload a new version that possibly fix call hang problem so test and report
and about ART problems i think the GAPPS is the issue so i left a ART supported GAPPS in the changelog
Many thanks @Shadow Of Leaf for that new release. :good:
Unfortunately the link regarding the new build seems not correct, it points to the previous "omni-4.4.4-20180817-jena-HOMEMADE" release. Also the internal build date seems the same. Or has the new build the same name like the old one?
If yes then it would make sense to add a V2 to the filename.
Regards
lorn10
lorn10 said:
Many thanks @Shadow Of Leaf for that new release. :good:
Unfortunately the link regarding the new build seems not correct, it points to the previous "omni-4.4.4-20180817-jena-HOMEMADE" release. Also the internal build date seems the same. Or has the new build the same name like the old one?
If yes then it would make sense to add a V2 to the filename.
Regards
lorn10
Click to expand...
Click to collapse
You Welcome
yes the name and build of V1 and V2 are the Same because i didn't build a new one
it is the old version with bugs fixed (i think)
you try it ???
Hi there Shadow Of Leaf
Thanks for the fast replay. Unfortunately the "hang on" issue is still the same like on the V1 build. It is not possible to hang up the call, - it stays open in the background.
The overall performance is really nice for that old phone hardware, - especially when the ART runtime is used. It feels a little bit better then CM11. And with Open Launcher v37 (v40 runs less fluid) the phone UI is looking more modern. Because of the smaller screen size, Open Launcher has to be adjusted somewhat. For everyone who want's to try it, I have uploaded in the attachment a v37 mini 2 config file. (I get the Open Launcher package from that side: https://f-droid.org/en/packages/com.benny.openlauncher/)
Unfortunately Android ART works only stable with certain really old GAPPS packages. The problems starts when these are updated automatically, the Google Apps stop working and are crashing randomly. I hoped that this problem is CM11 related, but Omni ROM 4.4.4 has the same issues. So this is most likely a fundamental problem of KitKat. It seems that Google has not designed the newer GAPPS packages Android "KitKat ART" compliant. In conjunction with ART, they may work properly only on "Lollipop ART" and above.
However, if I remember me right, I have read sometime something about these KitKat ART limitations. That may be a strange idea, but is it possible to "back-port" certain portions of Lollipop ART, like in the ART dex2oat tool, into KitKat? https://source.android.com/devices/tech/dalvik Well, maybe it's possible but the effort would be far too big...
Kind regards
lorn10
Here follows a short addition, - I have found an interesting XDA topic regarding KitKat ART vs. Lollipop ART. There is discussed the theoretical possibility to use the Lollipop "libart.so" in KitKat: https://forum.xda-developers.com/android/help/using-libart-android-l-kitkat-t2805745
Well, as assumed by me, this will be a BIG project. It's not so simple how it looks, the KitKat "libart.so" can't be just replaced with the Lollipop version. This concept to backport certain portions of a newer ART runtime back to KitKat is more a theoretical possibility, - not practical. A Backport of a "Android Go" version for the mini 2 would be more realistic then that...
lorn10 said:
Here follows a short addition, - I have found an interesting XDA topic regarding KitKat ART vs. Lollipop ART. There is discussed the theoretical possibility to use the Lollipop "libart.so" in KitKat: https://forum.xda-developers.com/android/help/using-libart-android-l-kitkat-t2805745
Well, as assumed by me, this will be a BIG project. It's not so simple how it looks, the KitKat "libart.so" can't be just replaced with the Lollipop version. This concept to backport certain portions of a newer ART runtime back to KitKat is more a theoretical possibility, - not practical. A Backport of a "Android Go" version for the mini 2 would be more realistic then that...
Click to expand...
Click to collapse
sorry for the bad news
i think that i fix the hang on call bug but it seems sophisticated one
i will try to to build a new version for s6500 and for s6500d also ( i don't how im gonna test it out, cause my sim card place in the phone seems to be broken)
for the ART i think in kitkat is just a preview for developers to test it out , not like lollipop is seems stable to use it
for the theory i think its possible but it need a lot of work and could not work (lollipop and kitkat are not alike so it well be a miracle if it work)
years late. but ... I have the S6500T version, all rom that I install fails to start
the apps are updated, but when it reaches the home screen the message "shutting down" appears even though the rom has started normally