Database Develop

[ROM][PORT]ChameleonOS For 926 & 925 [updated 20-November-2013]

{
"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"
}
Requirements:
Must be rooted!
Must be unlocked!
Must run a custom recovery!
What works?
Everything that I know of!
Are there bugs?
You flash and tell me!
(Navbar bug should be fixed as of 11/20/13)
Features can be found HERE.
Screenshots can be found in Tim's Original Thread
Thanks (in no particular order):
OSE
Bytecode
timpohladthomas
ChameleonOS
Razrqcom Dev-Team
Download:
ChameleonOS​

Will flash it tomorrow
Enviado desde mi Droid RAZR HD mediante Tapatalk

Will give this a shot tomorrow also.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Flashing right now, will post back in a few hours and let you know how it is running.
Edit: Flashing was smooth, installed the MIUI theme from goo.im and then reboot and am getting constant FC's on com.android.phone. As soon as I hit okay to accept it another one pops up. I am not sure if this is theme related or the ROM itself.
Also, there are no GAPPS included but I found them here: http://goo.im/devs/ChameleonOS/gapps
Edit 2: I tried installing the GAPPS from the above link and got stuck in a bootloop.

lysdexik said:
Also, there are no GAPPS included but I found them here: http://goo.im/devs/ChameleonOS/gapps
Edit 2: I tried installing the GAPPS from the above link and got stuck in a bootloop.
Click to expand...
Click to collapse
I just installed with the gapps from Cyanogen mod, the latest one on 4.3
It works perfectly
Btw, yea it's 4.3 if someone's wonders

I found a bug!
When you go in landscape mode, the navbar is completely bugged, and not possible to use.

I can not install any app that needs root, they say that I don't have root, is anyone else facing something like this?

Dexcellium said:
I found a bug!
When you go in landscape mode, the navbar is completely bugged, and not possible to use.
Click to expand...
Click to collapse
I'll make a new build when I can I'm pretty sure a fix has already been added to chaos' source.
Carcass.br said:
I can not install any app that needs root, they say that I don't have root, is anyone else facing something like this?
Click to expand...
Click to collapse
Check that you actually enable root, its not enabled by default so go into about phone and tap build # until it says you are now a developer to unlock the development settings where root is.
Edit- Links updated to new rom versions old versions are being uploaded to mediafire

@cj360 any way u can build this for the mb886 because the xt925 build works great but auto rotation and data wont work properly
Sent from my MB886 using XDA Premium 4 mobile app

Obviously cause its a different device. But I would rather help someone else build it as xt926,xt925,xt907 have one or two changes between them and when things work on one they'll work on all three and vice versa. As well as I just dont want to build for more than three devices.

Thanks mate, now my only problem is thoso random reboots when I try to listen something with a bluetooth headset

Android Pay after root?

I'm trying to get Android Pay to work after unlocking. I've tried Root Cloak module on Xposed, which solved similar issues on rooted phones in the past, but no luck.
I keep getting the error message below.
Any suggestions?
{
"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"
}

Read the chroma thread for nexus 6
Sent from my Nexus 6 using Tapatalk

spider623 said:
Read the chroma thread for nexus 6
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Link?

Sorry 6p, just Google Chroma 6P xda
Sent from my Nexus 6 using Tapatalk

rlmesq said:
I'm trying to get Android Pay to work after unlocking. I've tried Root Cloak module on Xposed, which solved similar issues on rooted phones in the past, but no luck.
I keep getting the error message below.
Any suggestions?
Click to expand...
Click to collapse
Just go to SuperSU and disable supersu. Then go to settings, app and open Android pay in all app tap. Then erase cache and data. Then open android Pay and tray the setting again.
Sent from my SM-N915F using Tapatalk
---------- Post added at 03:51 PM ---------- Previous post was at 03:49 PM ----------
dominguezcarlosm said:
Just go to SuperSU and disable supersu. Then go to settings, app and open Android pay in all app tap. Then erase cache and data. Then open android Pay and tray the setting again.
Sent from my SM-N915F using Tapatalk
Click to expand...
Click to collapse
If you use xposed this app doesn't work.
Sent from my SM-N915F using Tapatalk

Follow the instructions at the end of this post: http://forum.xda-developers.com/showthread.php?p=64199915
Essentially you have to flash unSU.zip to remove the current super user files, and flash the systemless supersu zip.
EDIT: Make sure you take a backup of your current ROM in TWRP, because I don't believe the systemless root has been tested on the turbo yet. If you want to wait a couple hours, I am planning on trying this out myself it a little while.

jwort93 said:
Follow the instructions at the end of this post: http://forum.xda-developers.com/showthread.php?p=64199915
Essentially you have to flash unSU.zip to remove the current super user files, and flash the systemless supersu zip.
EDIT: Make sure you take a backup of your current ROM in TWRP, because I don't believe the systemless root has been tested on the turbo yet. If you want to wait a couple hours, I am planning on trying this out myself it a little while.
Click to expand...
Click to collapse
Systemless only work with SDK 23, it mean Android 6.0.
Sent from my SM-N9200 using Tapatalk

Its like Samsung saying that the system is modified. Payment doesn't work maybe because Google doesn't want to take liability for a modified rom doing something wrong.
Sent from my ONE E1003 using Tapatalk

Android pay won't work on any rom that is not CTS compliant. That means, Samsung, LG, OnePlus, Cyanogen OS, HTC, etc will work. Custom ROMs will not work.
You'll also need to disable root. I use SuperSU and just disable root when I need to use pay. Works just fine.

dasunsrule32 said:
Android pay won't work on any rom that is not CTS compliant. That means, Samsung, LG, OnePlus, Cyanogen OS, HTC, etc will work. Custom ROMs will not work.
You'll also need to disable root. I use SuperSU and just disable root when I need to use pay. Works just fine.
Click to expand...
Click to collapse
I guess it's hit and miss. I'm on stock, bootloader unlocked, and I've tried it by disabling root - even uninstalled SuperSU and cleaned the cache in TWRP. I figured it's TWRP or that it's unlocked.
Is Xposed installed too?

Systemless Root benefits

Now that google has patched systemless root, are there any more benefits to it compared to the regular root?

If you're on full stock you can unroot and flash ota's. That's about it afaik

Raymondlikesroot said:
Now that google has patched systemless root, are there any more benefits to it compared to the regular root?
Click to expand...
Click to collapse
It's currently the only method to root stock rom and kernel. And leaving /system read only and untouched seems to be marshmallow's flavor if you will.

I have been on systemless for awhile now so perhaps it has changed but dont you need a modified boot image to avoid the corrupt phone message?
Sent from my Nexus 6 using XDA Labs

TonikJDK said:
I have been on systemless for awhile now so perhaps it has changed but dont you need a modified boot image to avoid the corrupt phone message?
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
"moddified boot image" is another way of saying custom kernel. whats wrong with custom kernels?

simms22 said:
"moddified boot image" is another way of saying custom kernel. whats wrong with custom kernels?
Click to expand...
Click to collapse
Nothing at all, I run franco's. But not having to mess with it if you are running stock is an advantage. A small one but that is what the op was asking.
Sent from my Nexus 6 using XDA Labs

Tonik09 said:
Nothing at all, I run franco's. But not having to mess with it if you are running stock is an advantage. A small one but that is what the op was asking.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
ops opinion then, as i enjoy custom kernels more :angel:

android pay works without having to toggle SU. saves a few clicks

synisterwolf said:
android pay works without having to toggle SU. saves a few clicks
Click to expand...
Click to collapse
not anymore, it doesnt since google shut it down for systemless root.

I wonder if you can use your google wallet card, within the android pay system and would it still work? I will have to test this...

simms22 said:
not anymore, it doesnt since google shut it down for systemless root.
Click to expand...
Click to collapse
On latest pn and I just used it to pay for dinner.
Sent from my iPhone 6s+ using Tapatalk
{
"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"
}

synisterwolf said:
On latest pn and I just used it to pay for dinner.
Sent from my iPhone 6s+ using Tapatalk
Click to expand...
Click to collapse
few possiblilities:
1. You haven't received the rollout for the new safetynet api
2. Your payment wasn't checked with safetynet this time.
3. You lucky booger.

I was going to say, they may not have "updated" android pay yet. I wonder if you don't update how that will work. Tbh, the systemless root does seem pretty moot at this point unless you love OTAs.

It is gonna get to the point that people will have to pick either root/custom roms or using things like android pay. Not a big deal personally as all mobile payments are blocked in every store here

[FIX] Stock Google Dialer 4.0+

Pretty straightforward: Flash with TWRP, get the latest Google Dialer from APK Mirror, and install it normally. No more restriction! Subsequent updates will install from the Play Store automatically.
{
"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"
}
For a better experience, make sure you change the default "Dialer" app under: Settings / Apps / Gear icon (top right) / Default Apps / Phone App
Download: View attachment GoogleDialer.zip

No way to do this without recovery then ?
Sent from my E6653 using Tapatalk

zippy01 said:
No way to do this without recovery then ?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
You can only install an older version 3.0RC8 I think

Phazonclash said:
You can only install an older version 3.0RC8 I think
Click to expand...
Click to collapse
Contact person name not shows only phone number.

GREAT! Thanks a lot @Phazonclash

sirdoha said:
GREAT! Thanks a lot @Phazonclash
Click to expand...
Click to collapse
Which version is fully working? is caller name is displaying.

saxena1 said:
Which version is fully working? is caller name is displaying.
Click to expand...
Click to collapse
I use latest version 4.0129037693 and it is working fine

saxena1 said:
Which version is fully working? is caller name is displaying.
Click to expand...
Click to collapse
Yeah. I use the same version with @toncheee

Would flashing this also make it work on a non xPeria device(Galaxy s7)?

bigpapa007 said:
Would flashing this also make it work on a non xPeria device(Galaxy s7)?
Click to expand...
Click to collapse
Please try and tell us!

bigpapa007 said:
Would flashing this also make it work on a non xPeria device(Galaxy s7)?
Click to expand...
Click to collapse
Yes, I'm using the latest stock Google Dialer on my S7 Edge at the moment without any issue.
That "fix" doesn't modify or replace anything in /system. It only adds two missing files on non-Nexus phones that are required to be able to install the latest stock Google Dialer:
com.google.android.dialer.support.xml under system/etc/permissions
com.google.android.dialer.support.jar under system/framework
Both files included come from the latest Nexus 5 Android 6.0.1 system dump

Just tried it on z5c and it works perfectly well. I am curious what happens if I uninstall the stock phone app through titanium backup pro and keep the Google dialer. Anyone tried it?
Sent from my E5823 using Tapatalk

Thank you, this got the Google dialer installed and working for me, I posted asking how to get Visual Voicemail to show up inside the Google Dialer, but setting it as the default app fixed that too

Phazonclash said:
Yes, I'm using the latest stock Google Dialer on my S7 Edge at the moment without any issue.
That "fix" doesn't modify or replace anything in /system. It only adds two missing files on non-Nexus phones that are required to be able to install the latest stock Google Dialer:
com.google.android.dialer.support.xml under system/etc/permissions
com.google.android.dialer.support.jar under system/framework
Both files included come from the latest Nexus 5 Android 6.0.1 system dump
Click to expand...
Click to collapse
I'm assuming since this adds files to /system that the phone would then fail SafetyNet checks? Meaning this would cause Android Pay to fail.

Devo7v said:
I'm assuming since this adds files to /system that the phone would then fail SafetyNet checks? Meaning this would cause Android Pay to fail.
Click to expand...
Click to collapse
I couldn't say. The files are official Android files and are present on every Nexus phones

New version out - Google Phone 5.1.131226882 (Extracted from the Pixel system dump).
Installed it on my Z5, working without problems for now!

Thank you for this.. Works great with new version

[Magisk v14] [GT-I9500] [Stock 5.0.1] Can't Use Magisk Hide and SafetyNet Check Fails

Hello, Everyone.
Just did a factory reset to my Samsung Galaxy S4 GT-I9500 (Black Edition) having Stock Android 5.0.1. Then I performed following steps:
I flashed TWRP 3.1.1 (using Odin) and that went well.
I took full backup in TWRP.
Then I downloaded Magisk Manager v5.3.0 from the official github releases link I got from this forum post. (can't insert link in the post since I'm new here)
Through Magisk Manager, I downloaded the latest Magisk-v14.0.zip
Installed Magisk-14.0.zip from TWRP. It showed no errors.
On rebooting the device, I confirmed root access using Root Checker.
(Here I had to update Google Play Services since they were pretty outdated due to Stock Firmware).
But now in Magisk Manager, I see that SafetyNet Check fails with following points:
ctsProfile: false
basicIntegrity: false
I also noted that I am unable to use Magisk Hide. If I check any checkbox in the list of apps shown in Magisk Hide and refresh the list, it automatically gets unchecked.
I also tried following points:
Disable Android Developer Mode
Use "Magisk Core Only Mode"
But nothing has helped so far.
Is there any way out of this that anybody can suggest?
Thanks in Advance!

I seem to be having the same problem with a Samsung S7
Magisk won't keep any of the settings I change.
Sent from my SM-G930F using XDA-Developers Legacy app

Josh Smith10 said:
I seem to be having the same problem with a Samsung S7
Magisk won't keep any of the settings I change.
Click to expand...
Click to collapse
Thanks for replying. Do you also see the same SafetyNet Check failures as mentioned above?

Your device is most likely running an unsupported kernel version: 3.4.0.
Magisk Hide does not support this kernel version and Magisk Hide will never work.
The only way you can possibly fix this is by installing a Custom ROM with a Kernel that has been up-streamed and has the missing feature that Magisk needs (mount namespace)

olivercervera said:
an unsupported kernel version: 3.4.0.
Click to expand...
Click to collapse
A little correction:
Galaxy S4 I9500 variant (Exynos one) uses Linux 3.4.5 instead of 3.4.0 in Qualcomm counterpart (I9505, etc).
Sent from my Redmi 3 using XDA Labs

swaroopb said:
Thanks for replying. Do you also see the same SafetyNet Check failures as mentioned above?
Click to expand...
Click to collapse
{
"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"
}
Nah, mate it fixes it up..
I'm running superman ROM..
Sent from my SM-G930F using XDA-Developers Legacy app

I did but have a read of this thread
https://forum.xda-developers.com/showthread.php?t=3600431
That should fix it
Sent from my SM-G930F using XDA-Developers Legacy app

Josh Smith10 said:
I did but have a read of this thread
https://forum.xda-developers.com/showthread.php?t=3600431
That should fix it
Click to expand...
Click to collapse
Could you tell me what you did exactly? Coz I'm having the same problem.

Faisal101 said:
Could you tell me what you did exactly? Coz I'm having the same problem.
Click to expand...
Click to collapse
I flashed the ROM then flashed the hot fix in twerp.
Sent from my SM-G930F using XDA-Developers Legacy app