Related
This is an Xposed module (See http://forum.xda-developers.com/showthread.php?t=1574401 for more on Xposed) that allows Netflix to work on CM10.1 on Exynos4 devices.
Source code is at https://github.com/Entropy512/XposedNetflixWorkaround - Use the Android Developer Tools Eclipse package to build it
To install:
Install the Xposed Installer APK from the thread linked above
Install the Xposed framework using Xposed Installer
Install the APK linked in this post
Reboot your device after enabling the module in Xposed Installer
Enjoy Netflix
How does this work?
For whatever reason, Netflix uses its own player, called JPlayer, if it detects that it is running on Android 4.2. For whatever reason, JPlayer does NOT like the current video subsystem in CM10.1 on Exynos4 devices.
What this module does is make Netflix always think that it is running on ICS, which will make it use what appears to be the system OMX player. (I'm not entirely sure of this, but I am sure that it is NOT JPlayer and it DOES work on all of my devices I've tested).
This is an interim workaround/hack until the root cause of JPlayer failing on Exynos4 devices can be determined. (Edit: From talking with a few people, JPlayer is replacing a number of components of Android's playback framework. This includes components that have been altered for Exynos4 compatibility.)
DO NOT REPORT THIS ISSUE IN CYANOGENMOD JIRA. No affected devices are receiving M or stable builds and this is one of the many reasons.
reserved 2 - probably not needed
Worked perfect thanks
Sent from my GT-N8013 using xda premium
I'm having issues installing Xposed - after I install the apk and hit the install button, it throws the error "cannot read /data/xposed/modules.whitelist".
Netflix still a no go for me!
Sent from my GT-N8013 using Tapatalk 2
Worked on the U2.
Sent from my Nexus 4 using Tapatalk 2
BeardedB said:
Netflix still a no go for me!
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
Working here... More details please?
dpwhitty11 said:
I'm having issues installing Xposed - after I install the apk and hit the install button, it throws the error "cannot read /data/xposed/modules.whitelist".
Click to expand...
Click to collapse
Could you try this installer instead? http://forum.xda-developers.com/showthread.php?p=36436643#post36436643
It's a known problem for some ROMs which fail to update /data/system/packages.list.
rovo89 said:
Could you try this installer instead? http://forum.xda-developers.com/showthread.php?p=36436643#post36436643
It's a known problem for some ROMs which fail to update /data/system/packages.list.
Click to expand...
Click to collapse
Worked perfectly, thanks!
Sent from my GT-N8013 using Tapatalk HD
Andrew, version 1.8.1 of Netflix works on Exynos4 + Jelly Bean. I'm not sure if it's the last known working version but it's an alternative; I took a stab and downloaded the version I thought might be at/around the last Netflix update for ICS.
Edit: arcee indicated that 2.1.1 will work in tomorrow's build, not sure if specific to Odroid only.
CMNein said:
Andrew, version 1.8.1 of Netflix works on Exynos4 + Jelly Bean. I'm not sure if it's the last known working version but it's an alternative; I took a stab and downloaded the version I thought might be at/around the last Netflix update for ICS.
Edit: arcee indicated that 2.1.1 will work in tomorrow's build, not sure if specific to Odroid only.
Click to expand...
Click to collapse
He took a different approach to killing JPlayer:
https://github.com/CyanogenMod/andr...mmit/916bbf03847ef5e3b5264bbbeac6c30399281520
So this Xposed mod may become obsolete...
There's no clean way to do this. Either there is app-specific **** in the device tree that is difficult for users to remove if it ever gets derpy, or users have to actively search for a workaround such as this one.
Entropy512 said:
He took a different approach to killing JPlayer:
https://github.com/CyanogenMod/andr...mmit/916bbf03847ef5e3b5264bbbeac6c30399281520
So this Xposed mod may become obsolete...
There's no clean way to do this. Either there is app-specific **** in the device tree that is difficult for users to remove if it ever gets derpy, or users have to actively search for a workaround such as this one.
Click to expand...
Click to collapse
Latest working version is 2.0.1, the APK is linked below. It is the last version before they have introduced the newest controls. Works just fine on S2 with CM 10.1.
http://www.mediafire.com/?4ra0wf9h441r1oo
This is the easiest solution for the problem right now. Don't update from Market, but that is I guess quite obvious.
kokesh said:
Latest working version is 2.0.1, the APK is linked below. It is the last version before they have introduced the newest controls. Works just fine on S2 with CM 10.1.
http://www.mediafire.com/?4ra0wf9h441r1oo
This is the easiest solution for the problem right now. Don't update from Market, but that is I guess quite obvious.
Click to expand...
Click to collapse
The Xposed solution allows you to update and install from the Market with no issues.
Arcee's "patch the configuration XML file" approach also works.
Entropy512 said:
The Xposed solution allows you to update and install from the Market with no issues.
Arcee's "patch the configuration XML file" approach also works.
Click to expand...
Click to collapse
I know, but I can't get it to work on my 2013-01-17 CM10.1 nightly S2, this was the best way to fix it.
Xposed can't install.
Entropy512 said:
reserved 2 - probably not needed
Click to expand...
Click to collapse
Is this something that will eventually be rolled into a cm 10.1 nightly update or will it always be something that has to be installed separately on the side? Thanks again for all your awesome work.
mauidiver40 said:
Is this something that will eventually be rolled into a cm 10.1 nightly update or will it always be something that has to be installed separately on the side? Thanks again for all your awesome work.
Click to expand...
Click to collapse
Dependent on the device maintainer I'm sure. My Odroid U2 has a fix merged in last night's nightly. YMMV.
Entropy512 said:
He took a different approach to killing JPlayer:
https://github.com/CyanogenMod/andr...mmit/916bbf03847ef5e3b5264bbbeac6c30399281520
So this Xposed mod may become obsolete...
There's no clean way to do this. Either there is app-specific **** in the device tree that is difficult for users to remove if it ever gets derpy, or users have to actively search for a workaround such as this one.
Click to expand...
Click to collapse
Any chance of adding this to Galaxy S2 nightlies?
I've added <int name="nflx_player_type" value="6" /> manually to the config file and it works.
mauidiver40 said:
Is this something that will eventually be rolled into a cm 10.1 nightly update or will it always be something that has to be installed separately on the side? Thanks again for all your awesome work.
Click to expand...
Click to collapse
I'm considering using arcee's approach... I really dislike having app-specific **** in the device tree though...
I can't figure out why people are having issues installing Xposed - it has installed flawlessly on every CM10.1 device I've tried. The fact that it may fail on certain manufacturer-customized firmwares isn't relevant here as this hack is specific to CM10.1
The only thing I can think of might be that Superuser prompts aren't quite working right on some people's devices.
As to eventually including Xposed in CM itself - It is something I would love to see, however as a device maintainer, it's "above my pay grade". Including it directly in CM would require careful consideration and analysis by the project leads.
I'm working on a flashable zip that drops a script in init.d to get the job done. The script is based on https://github.com/CyanogenMod/andr...mmit/916bbf03847ef5e3b5264bbbeac6c30399281520 although I had to tweak it a little to get it to work. I can share it once it is finished, if anyone is interested. It will also copy a script to addon.d so that as I update cm10.1, the hack will be persistent.
No-name CM10.2 nightlies
NOTE: THIS IS A WORK IN PROGRESS. CONTRIBUTIONS ARE WELCOME!
(see build setup detailed below)
With that said: Welcome to the No-name CM10.2 nightlies ROM.
Who is this ROM for?
This is a ROM for people who are so eager to try bleeding edge software that they are willing to test-drive it, all bugs included, while it is being developed.
If you value a stable daily-driver with a minimum of issues over everything else, this ROM is probably not for you. There will be bugs. CM10.2 is still in early phase of development, after all.
What's working:
Wi-Fi
GPS
Headphone
All docking stuff
CM Features
AOSP Keyboard
Bluetooth
Micro SD Card & Internal storage
Launcher
Lockscreen
Auto rotate
Camera (99%)
YouTube HD playback
Unresolved, confirmed issues
Front facing camera in Camera app (works in Skype etc)
CM Focal (OMX Codec issue)
Installation:
If coming from any non-4.3.x/CM10.2-based ROM, a factory reset is very much recommended.
Although CM does have official instructions for just upgrading from 10.1.
(0. Backup your existing ROM)
1. Download latest nightly to device.
2. Download special TF101 4.3 gapps linked below.
3. Boot into recovery. TWRP is recommended over CWM.
4. Flash ROM. (This also wipes /system and any mods you already have.)
5. Flash special TF101 Gapps.
6. Reboot.
Basically, the normal procedure for any ROM.
No-name parts with extra features can optionally be installed from market.
If you feel like donating, you can install Straitjacket which is my paid app with some extra features. Plus it might give you a warm fuzzy feeling for being a good guy.
Downloads
TF101 (Wifi only) ROM is available here:
- nexfiles
TF101G ROM is available here:
- nexfiles
4.3 Gapps available here:
- Special TF101 gapps by dlumberg & josteink.
- dlumberg's mirror
Thanks to:
- The Cyanogenmod team, for all the goodies they keep on delivering, across devices.
- RaymanFX, for a CM-compatible device-tree for the TF101.
- Timduru, for KatKernel which keeps this thing stable and functional.
Issues?
Probably plenty. Help us out by reporting them here in this thread. Leave the github issue-tracker alone for now.
If you think you can fix anything, feel free to contribute. We're nice people and open to contributions.
Sources:
Android is open-source. This is an open-source project.
Cyanogenmod:
https://github.com/CyanogenMod/
Noname projects:
https://github.com/NonameROM
Kat-kernel:
https://github.com/timduru/tf101-katkernel
Build-setup:
https://github.com/josteink/android_multi-build
https://github.com/josteink/simba
Current contributors:
- dlumberg
- TheMrcool212
- ShevT
- Jostein Kjønigsen (josteink)
Changelog:
2013-08-12: Initial (preliminary) thread posted, with preliminary build instructions.
2013-08-17: Added tabletUI mods.
2013-08-17: Added TF101G build to setup.
2013-08-20: Youtube HD and Camera fixes.
2013-08-20: Added Noname top-level project on github.
2013-08-21: No longer considered experimental.
(Preliminary) Build instructions:
If you want to contribute, it's probably a good start to get your own build working.
See the instructions here:
https://github.com/NonameROM/android/wiki/Building-Noname-ROM
TheMrcool212 said:
I'm using Ubuntu 13.04 64-bit too. Maybe you had unmerged commits that causing the error.
EDIT: They had fix it:
https://github.com/CyanogenMod/andr...mmit/9de697245289afc7bb88b8e71301e2fab17a0a31
Click to expand...
Click to collapse
I can second that this issue is no longer present, but now I get things related to bionic/libc (for NetBSD!!!) instead...
Don't think it's really realated, but I just want to make sure we don't have any differences which can affect the result. What version of Java are you running?
This is mine:
[email protected]:/mnt/build/android/tf101/4.3$ java -version
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
Click to expand...
Click to collapse
Great to see this!! Thx Josteink.
Been fooling around with Katkiss 4.3 on a spare tf101 I have, if No-name will be like that then our beloved tf will keep on living!!!!!
Thx to all devs
Sent from my Transformer using xda premium
josteink said:
I can second that this issue is no longer present, but now I get things related to bionic/libc (for NetBSD!!!) instead...
Don't think it's really realated, but I just want to make sure we don't have any differences which can affect the result. What version of Java are you running?
This is mine:
Click to expand...
Click to collapse
This commit was the cause of the bionic/libc error. I got this before too, so i skipped that commit. I recommend to use my android_bionic repository, replace it with the current CM10.2.
https://github.com/TheMrcool212/android_bionic/tree/cm-10.2
For the java, i got the same version too:
Code:
[email protected]:~$ java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.13.04.2)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
What's working (Tested on my own stock CM10.2 build)
Bluetooth
Dock battery & keyboard layout.
USB Dock (Only tested with pendrive) & SD Card
Micro SD Card & Internal storage
Launcher
Lockscreen
Auto rotate
Confirmed issues
AOSP Keyboard crashes on certain time, even when not using it
Camera & CM Focal
Weird window animation bug when going to home screen.
Back button doesn't work, even on keyboard (I used pie instead)
Menu button, even on keyboard too.
What's not confirm yet to be working
Wi-Fi (due to keyboard issue)
GPS (No Wi-Fi access)
The build of mine and him are just the same, since we are using the same repositories.
TheMrcool212 said:
This commit was the cause of the bionic/libc error. I got this before too, so i skipped that commit. I recommend to use my android_bionic repository, replace it with the current CM10.2.
https://github.com/TheMrcool212/android_bionic/tree/cm-10.2
For the java, i got the same version too:
Code:
[email protected]:~$ java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.13.04.2)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
Click to expand...
Click to collapse
Cool. Fixed it. Uploading build now
TheMrcool212 said:
What's working (Tested on my own stock CM10.2 build)
...
lots of useful info
...
Click to expand...
Click to collapse
Awesome. Copied to FP!
Added this ROM to the general build setup.
Will find out if it works tomorrow
i will still stick with your wonderful 10.1 rom but thank you for your hard work.
The tf 101 community despite some problems is legendary in its character.
Sent from my Transformer using xda premium
karapoutsoglou said:
i will still stick with your wonderful 10.1 rom but thank you for your hard work.
The tf 101 community despite some problems is legendary in its character.
Sent from my Transformer using xda premium
Click to expand...
Click to collapse
+1, but will follow this thread with more than average interest
Note top self/personal reminder:
- try flashing Google keyboard on top of AOSP keyboard.
- try building with non generic cpu variant which is not cortex-a9 from twrp device tree. Might be better than generic and still work.
Sent from my Galaxy Nexus using Tapatalk 4
josteink said:
Note top self/personal reminder:
- try flashing Google keyboard on top of AOSP keyboard.
- try building with non generic cpu variant which is not cortex-a9 from twrp device tree. Might be better than generic and still work.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Google keyboard works perfectly for me using banks gapps.
@josteink Just want to tell you:
I made a branch called " tf101g-jellybean_4.3 " , based on ShevT's TF101G device tree. I've merged all of 4.3 commits from TF101 branch to the TF101G branch as well. We'll start making this ROM for 3G version as soon as the ROM for TF101 version are quite stable.
diogo.sena said:
Google keyboard works perfectly for me using banks gapps.
Click to expand...
Click to collapse
Where's the banks gapps, can you give me the link for it?
TheMrcool212 said:
@josteink Just want to tell you:
I made a branch called " tf101g-jellybean_4.3 " , based on ShevT's TF101G device tree. I've merged all of 4.3 commits from TF101 branch to the TF101G branch as well. We'll start making this ROM for 3G version as soon as the ROM for TF101 version are quite stable.
Click to expand...
Click to collapse
Agreed.
I just think letting @ShevT open up his repo and give us commit access would be "cleaner". We'll see when he discovers this thread and wants in on the action
TheMrcool212 said:
Where's the banks gapps, can you give me the link for it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2012857
Should probably be added to FP. I'll get it done.
I know the original gapps (4.2 no-name ROM version) Google keyboard had some issues, but the newly released Google keyboard from the play store worked fully on the 4.2 no-name ROM. Not sure if there is a newer gapps which now contains that same keyboard or if it needs to be installed from the play store?
Sent from my Nexus 4
diogo.sena said:
Google keyboard works perfectly for me using banks gapps.
Click to expand...
Click to collapse
Can you confirm if wifi or GPS is working then? Will make the list on the first page easier for people to rate
And what version did you use? The 4.3 version?
I just flashed the banks' 4.3 Google Keyboard. Now i can have access to my Wi-Fi and here's the update:
Wi-Fi is working
GPS working too!
All dock functions are working when flashing the banks' Google Kayboard gapps
Back, menu and recents button are working (I'm not sure why this had been fixed, maybe due to the working keyboard)
No AOSP keyboard crashes.
New issue
YouTube doesn't play when HD is enabled, only when it's been disabled.
What's left
Camera & CM Focal
Weird window animation bug when returning to home screen.
YouTube player issue.
@josteink, I think we need to revamp the gapps, since some of the apps are not updated like the keyboard, PlayStore, Google Search etc.
TheMrcool212 said:
I just flashed the banks' 4.3 Google Keyboard. Now i can have access to my Wi-Fi and here's the update:
Wi-Fi is working
GPS working too!
Click to expand...
Click to collapse
Yes, only wifi droped one at restoring all the apps from Google, while loading the app store. After that no problems with wifi.
TheMrcool212 said:
New issue
YouTube doesn't play when HD is enabled, only when it's been disabled.
Click to expand...
Click to collapse
Is same as on KatKiss http://forum.xda-developers.com/showpost.php?p=44274292&postcount=2
Using TWRP 2.3.2.3
I did a cache, and system wipe, factory reset and flashed the rom with the Banks Gapps, just the core.
Main issue: lost root privilages. Otherwise: feels already as a matured rom
---------- Post added at 09:16 AM ---------- Previous post was at 09:09 AM ----------
pinkdot;44604445
Main issue: lost root privilages. [/QUOTE said:
Ah, got root back by changing the settings
Click to expand...
Click to collapse
Introduction
Firefox OS, also known as Boot2Gecko, is a lightweight mobile OS made by Mozilla, based around HTML5. http://en.wikipedia.org/wiki/Firefox_OS
This is an unofficial build of FirefoxOS for flo and deb.
What does not work:
MTP
Mobile data (on LTE version of N7)
Not really smooth
Installation
These ZIP files act like an Android ROM, so the installation is the same as usual - do a factory reset in recovery and flash the ZIP file.
Downloads
Version 1.2 (stable): b2g_flo_1.2_20131011-2.zip
Version 1.3 (in development): b2g_flo_1.3_20140207.zip
Source code
All source code is from official B2G repositories.
Device folder: https://github.com/Tasssadar/android_device_asus_flo/tree/b2g-4.3_r2.1
Manifest for flo: https://gist.github.com/Tasssadar/6933349
Other than that, B2G sources are used.
Sweet. Nice man!
Going in my multirom now!
Sent from my Nexus 7 using Tapatalk 4
any chance to support LTE version?
thanks
Thank you so much for this. I tried to look at doing it myself but had not had time to fully read and figure it out. Can't wait to see this in action.
hkfriends said:
any chance to support LTE version?
thanks
Click to expand...
Click to collapse
It supports DEB, there's just no LTE signal.
it won't boot. I get a pink screen. Could it be the host kernel I use? I thought this would load whatever kernel was in the new ROM. I use glitch kernel for latest CM nightly.
Sent from my Nexus 7 using XDA Premium HD app
Looks cool, downloading now!
Sent from my Nexus 7 using XDA Premium HD app
Cool !!!
Good job
Please continue this developement
and 1.2 not freeze soruce , it mean it will have new source come from mozilla if found bug
and buletooth work on this? fantastic how you do it?
----------------------------------------
about your file ? why you merge system and data in same file? (it a stupid question)
sorry for my bad english !
downloaded and installed with no problem...
by the way, how to take screenshot as there's no home button? :/
pureexe said:
Cool !!!
Good job
Please continue this developement
and 1.2 not freeze soruce , it mean it will have new source come from mozilla if found bug
and buletooth work on this? fantastic how you do it?
----------------------------------------
about your file ? why you merge system and data in same file? (it a stupid question)
sorry for my bad english !
Click to expand...
Click to collapse
No, bluetooth does not work. It acts as if it would, but it won't find any devices.
Why wouldn't I put system and data in one file? It belongs together, /system contains gecko.
lightson said:
downloaded and installed with no problem...
by the way, how to take screenshot as there's no home button? :/
Click to expand...
Click to collapse
Settings -> Device information -> More information -> Developer -> Enable software home button
Tasssadar said:
Settings -> Device information -> More information -> Developer -> Enable software home button
Click to expand...
Click to collapse
thanks, will try that again later :good:
Tasssadar said:
No, bluetooth does not work. It acts as if it would, but it won't find any devices.
Why wouldn't I put system and data in one file? It belongs together, /system contains gecko.
Click to expand...
Click to collapse
But webapps contain in /data/local/webapps ?
or /system/b2g/webapps on your build?
Those are just apps, gecko itself is in /system/b2g, and I suppose it differs between firefoxOS versions.
@Tasssadar
easier to make flashable zip
extract this file into B2G/out/host/linux-86
and run
Code:
./build.sh otapackage
Just got it running in multirom, works alot better then i expected! Thanks Tassadar, this will be fun to play around with :silly:
I too finagled this to work with MultiROM!! Thanks Tassadar, this is pretty baller.
Nice @Tasssadar !
I'll flash this once I get home and give her a whirl.
Tasssadar said:
Introduction
Firefox OS, also known as Boot2Gecko, is a lightweight mobile OS made by Mozilla, based around HTML5. http://en.wikipedia.org/wiki/Firefox_OS
This is an unofficial build of FirefoxOS for flo and deb.
What does not work:
Camera
MTP
Mobile data (on LTE version of N7)
Bluetooth
Not really smooth
Installation
These ZIP files act like an Android ROM, so the installation is the same as usual - do a factory reset in recovery and flash the ZIP file.
Downloads
Version 1.2 (stable): b2g_flo_1.2_20131011-2.zip
Version 1.3 (in development): b2g_flo_1.3_20131010.zip
Source code
Device folder: https://github.com/Tasssadar/android_device_asus_flo/tree/b2g-4.3_r2.1
Manifest for flo: https://gist.github.com/Tasssadar/6933349
Other than that, B2G sources are used.
Click to expand...
Click to collapse
Don't know if anyone else said this but if you try to use the notification bar in 1.3, it will just stay down and won't go away. I know it is in development. Also can we flash a custom kernel for it that does not use the Kexec patch?
WeRSpecialPeople said:
Don't know if anyone else said this but if you try to use the notification bar in 1.3, it will just stay down and won't go away. I know it is in development.
Click to expand...
Click to collapse
Touch the notif bar (top of your screen) again to hide it.
Sent from my Nexus 7 using xda app-developers app
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimRoms Tilapia, ROM for the Nexus 7
Contributors
dexter93, Tylog, SlimRoms
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2015-01-02
Last Updated 2015-01-01
Some hints:
1. Be sure you are on latest CWM or TWRP recovery!!!!!!
2. Not all gapps packages right now are nice working. You can try others but at least I know that the one linked here is working. If you have other gapps which are working you can link it here of course
3. Full wipe when coming from any 4.3 or 4.4 rom (as well format system manually please)
Reporting Bugs
When you submit a bug you want to make sure that nothing from your side is causing it. Otherwise your developer might be hunting a bug which doesn't really exist.
The best way to achieve this is by doing the following.
1. Make a nandroid backup.
2. Perform a full wipe (factory reset + wipe /system)
Now we have two different ways depending on what kind of problem you're having.
3a. When you're having a problem with a ROM function, flash just the ROM without GAPPS etc. and boot back into the system. You will boot directly onto the homescreen.
3b. When you're having a problem with a 3rd party app in combination with our ROM then flash the ROM and GAPPS.
Boot now back into the system. You will boot to the setup wizard.
Log in to your Google account but make sure that you untick "Restore from my Google Account to this phone/tablet".
Finish the setup and open the playstore and download only the app you're having problems with.
4. Start a logcat recording and reproduce the bug (if possible more than once) while taking the logcat. If you don't know how to get a logcat read this tutorial or this.
5. Post the logcat in a txt file (this is important because you otherwise clog up the threads with your log) in the correct thread.
Please also write detailed description how we can reproduce the bug.
6. Restore your backup from point 1 and wait for a fix (don't ask for ETAs).
@kufikugel The recovery linked in post #2 is for the Galaxy Nexus (maguro)
kufikugel said:
Hey guys,
as you know SlimTeam does not own anymore tilapia......so this build is currently completly untested. Means...do a nandroid before please and give feedback.
thanks and cheers and have fun
kufi
Click to expand...
Click to collapse
so sad to hear slimteam does not own anymore tilapia.. anyway, thanks for hard work..
Flashed. ?. It booted fine, no need to wipe like in 4.3. 3g is working, and i didn't have to manually insert apn data. But there are no slim options in settings ?.
Thanks
PS: the new Google launcher is in this gapps.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Well I'm happy with maguro version, son I'll try this one with my tilapia tablet. Thanks
Installed and restoring apps from store. No problems at this moment.
Is any way to get "tablet mode" for this rom?
Can i just use twrp?
webnorka said:
Well I'm happy with maguro version, son I'll try this one with my tilapia tablet. Thanks
Installed and restoring apps from store. No problems at this moment.
Is any way to get "tablet mode" for this rom?
Click to expand...
Click to collapse
no
kamaliqwan said:
Can i just use twrp?
Click to expand...
Click to collapse
latest 2.6.3.2 will work
Sent from my Nexus 4 using Tapatalk
Stable, usable, but without auto-rotate isn't full-fuctional(
great work
Stable and fast, I'm using faux kernel but I can't get that darn rotation fixed/ ultimate rotation will work for now.
Thanks for the tilapia love.
android88 said:
no
latest 2.6.3.2 will work
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
thanks for the reply & info.. :good:
i just flash via latest cwm..and it works great..! :highfive:
for now..i just noticed that keyboard is keep showing on homescreen & screen rotation is not working...
keep it up guys! and i have the new Nex7 deb and would like to have SlimKat runnin on it too!!
i can be the tester if u need one
new build is up guys
changes see 2nd post OP
have fun and report back please
kufikugel said:
new build is up guys
changes see 2nd post OP
have fun and report back please
Click to expand...
Click to collapse
Just flashed 1st alpha build earlier today and already an update! Sweet! Thanx! :thumbup:
Sent from my SGH-M919 using xda app-developers app
Just flashed your latest build GPS works sometimes and OK google works fine location doesn't activate in Google now it just keeps on saying turn on location services! Great job though
edit: did a factory reset and full wipe and all works fine
Sent from my Nexus 7 using Tapatalk 4
During bootup, error "Unfortunately, messaging has stopped". Not a big deal though, but if anyone feels like getting rid of that, it is the mms.apk that needs to be deleted.
Other than that, everything else seems fine.
Sent from my Nexus 7 using Tapatalk 4
zard said:
During bootup, error "Unfortunately, messaging has stopped". Not a big deal though, but if anyone feels like getting rid of that, it is the mms.apk that needs to be deleted.
Other than that, everything else seems fine.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
yeah..same error here.and camera also no go..
but others is good..hope tiles customizations coming soon..its the most important features..!
for camera we just need to wait for the 4.4 binaries google will hopefully release soon. I think the effort to hack now around to get the old camera blobs working and then reverting in some days back to the new is not really usefull. So a bit wait on camera
Mms....lmao unbelievable that google still not solved it in the source....next build will have mms fixed Man everything we need to do on our own
hehe
cheers
new version is up guys
with mms fix
Fixes new version:
- added dalvik optimizations....so speed up step one
- reworked and adapted status bar clock and date customization to 4.4
- added some of our camera features (smart captchure, jpg quality, color filter, gps indicator)
- reworked the complete camera to the new google style. Google stoped it after they finished the photo camera interface lol. So all into new PIE style + some fixes + more consistent now
- added a bunch of Mms/SMS fixes
- activated on supported devices lockscreen transparency on nav and statusbar
- some stability fixes
- fixed some google 4.4 code derps
- a lot small stuff
have fun and cheers
PS. the camera features for tilapia of course you cannot use right now
Cool ROM! i like it, but i hope more performance optimization coming
CM11.0 for Milestone2
[Downloads][gapps]
It's based on defy(made by Quarx) version.
Changelog:
22.12.2014 - smartass governor added; CM code synced; MERRY CHRISTMAS AND A HAPPY NEW YEAR
03.10.2014 - CM code synced
18.07.2014 - CM code synced (4.4.2 -> 4.4.4)
30.05.2014 - CM code synced
12.03.2014 - Some small BT headset changes; CM code synced(seems to fix some random reboots/telephony layer problems seen in last 2 versions).
24.02.2014 - Call delay fixed
22.02.2014 - BT headsets should now work(haven't tested it myself); CM code synced
20.01.2014 - wifi tethering fixed(this time for good I hope); OTG support added; CM code cynced.
18.12.2013 - wifi tethering partially fixed(see notes); CM code synced.
12.12.2013 - battery charge level shown in 10% steps fixed; incorrect colors during video playback(introduced in previous build) fixed; CM code synced(android updated: 4.4.1->4.4.2);
09.12.2013 - baseband selection fixed; apps2sd disappearing after reboot should be fixed(haven't tested it); CM code synced(android updated: 4.4 -> 4.4.1, luncher settings added...); persian language(fa_IR) added; new gapps(4.4.1) available
03.12.2013 - bluetooth fixed; green led disabled after boot; CM code synced; ringtones restored; following languages supported: en_US pl_PL ru_RU zh_TW de_DE es_ES cs_CZ it_IT vi_VN pt_BR hu_HU fr_FR zh_CN nl_NL
02.12.2013 - proximity sensor fixed(main reason to release this version so quickly after the previous one); camera fixed; baseband selection tool added; CM code synced; still on old kernel; almost all ringtones removed(to make space for Camera app) - they will be restored(with the apps removed already) in the next version.
29.11.2013 - dialer and incoming voice level fixed; CM code synced; still on old kernel
25.11.2013 - CM11 - wifi fixed, keyboard backlight fixed, CM code synced(quick settings added among others); Some apps(Email, Camera, Video Editor) removed so that gapps will fit on the /system; AOSP discontinued
13.11.2013 - AOSP: wifi fixed; apps installation from sdcard fixed; camera preview working(taking photos/recording does not work yet); ART seems to work
08.11.2013 - CM11: Initial version
NOTES:
Use minimal/core gapps(about 20MB) from the link above
Known issues:
Sources:
repo init -u git://github.com/czechop/android.git -b cm-11.0
Installation
Install my CM10.2 version >= 07.11.2013 first
Go to recovery
Make a backup of your data(highly recommended)
Install this ROM
Install core gapps
If you wiped data(made factory reset) before installation, then after installing ROM boot it first, and then reboot and install gapps(otherwise you may get setup wizard crashes)
Credits:
Credits for this rom goes to: Quarx2k, Tezet, Blachd0se, CM team... and many, many more.
I must admit, you're very quick.
Hope bugs will be removed fast. If so many things are not working yet, I'll wait. Right now I'm more than satisfied with your JB release. Regards!
WOW!!! That's so fast!!!! hehehhe
I agree with Rabinhood. Your JB ROM are great!
Congratulations and thank you so much!!!
Fast
Enviado de meu A953 usando Tapatalk
Thanks czechop, that's amazing! let's rock the ms2!
really looking forward to this...good luck czeshop,your cm10.2 rocking my MS2:laugh:
Does cm11 include an updated (trebuchet) launcher? If so, will I be able to grab it and use it on cm10.2?
Sent from my Milestone 2 with tapatalk 4
divie said:
Does cm11 include an updated (trebuchet) launcher? If so, will I be able to grab it and use it on cm10.2?
Sent from my Milestone 2 with tapatalk 4
Click to expand...
Click to collapse
In /system/app there's no Trebuchet.apk (it was there in 10.2). I haven't tried this ROM, but it looks like there is no Trebuchet here. Or it has a different file name.
divie said:
Does cm11 include an updated (trebuchet) launcher? If so, will I be able to grab it and use it on cm10.2?
Sent from my Milestone 2 with tapatalk 4
Click to expand...
Click to collapse
It does contain updated trebuchet. You can grab it from the zip(something like Luncher3 or similar).
czechop said:
It does contain updated trebuchet. You can grab it from the zip(something like Luncher3 or similar).
Click to expand...
Click to collapse
Yupp, my mistake, there's Launcher3.apk in /system/app.
[EDIT]
But... I cannot install it. Installer says package is broken.
Guys, any idea how is the memory usage? Is it really for low end devices.
Thanks for ur work dev!
Sent from my ME722 using xda app-developers app
@czechop can you post some photos about the rom? (Who does it look like, etc...)
The time has come. I'm. Installing it.
[EDIT]
I was too fast again. Well... First thing is TRWP refused to install gapps. The other: I coudn't restore my apps with Titatium Backup since it couldn't gain root access. I'll try the next release.
Besides, I like the new tap button sound. It's less offensive than the previous one.
[EDIT 2]
Downloaded some other zip with gapps for 4.4, flashed and... phone died - I even cannot enter bootmenu.
So that's the story for today.
[EDIT 3]
Finally after 3 hours I'm when I started at the beginning.
Besides, does any of you have a flashable zip file with TRWP which from one hand can be flashed with an old CWM recovery (the one from droid2bootstrap), and from other hand can flash latest 10.2 ROMs? If I had something like that, I would save 2 hours of work...
rkrisi said:
@czechop can you post some photos about the rom? (Who does it look like, etc...)
Click to expand...
Click to collapse
It looks similart to 4.3. Not so blue - more grayish blue tint. Also screen font is more compact (similar to that Nokia had on Symbian devices). Quite smooth, at least as smooth as 4.3 - but I didn't have a chance to test it deeper.
And now what the matter with your phone? You have to flash sbf, and do everything (rooting,etc...)from the beggining?
Sent from my ME722 using xda app-developers app
rkrisi said:
And now what the matter with your phone? You have to flash sbf, and do everything (rooting,etc...)from the beggining?
Click to expand...
Click to collapse
Yes, I've already done it.
SBF -> root -> bootstrap -> CM10 -> Engle's CM10.1 -> Czechop's 10.2
If only I had a TRWP zip which can be flashed from old boostrap app the way would be shortened to:
SBF -> root -> bootstrap -> TRWP -> Czechop's 10.2
And another interesting thing. The biggest problem of MS2 is a locked bootloader, yes? But thanks to it I didn't brick my phone. I'm using Linux and usually flash SBF from inside a VirtualBox Windows machine. Today something went wrong, and virtual machine froze during early flashing stage. I had to disconnect MS2 during flash. At that point when I put battery, a screen similar to power+camera+vol_up appeared saying that code is broken, but I was still able to flash SBF again (this time under "real" Windows). Lucky me, because I thought I will have to upgrade my phone and leave MS2 threads.
hey guys!!!
Sorry for my ignorance, but, what's the difference between the cm11 download and the AOSP download???
Thanks!!
yuriaps said:
hey guys!!!
Sorry for my ignorance, but, what's the difference between the cm11 download and the AOSP download???
Thanks!!
Click to expand...
Click to collapse
AOSP is hard google code as is, and cm11 is a customization of AOSP.
Hello.
So I moved one small step further: managed to root AOSP 4.4 with an app called Kingo Android Root (very easy one click method performed under Windows - there are some information that it looks suspicious, and some suggest it might install some malware, but for me it worked like charm).
Now there's one more thing that prohibits me from daily use. I have no mobile data access - I can call phone, but data connection is possible only with wi-fi. Has any of you encountered such problems?
And last: I'm not able to install gapps provided in first post. Is anyone else affected too?
Thanks
Chris
rabinhood said:
Hello.
So I moved one small step further: managed to root AOSP 4.4 with an app called Kingo Android Root (very easy one click method performed under Windows - there are some information that it looks suspicious, and some suggest it might install some malware, but for me it worked like charm).
Now there's one more thing that prohibits me from daily use. I have no mobile data access - I can call phone, but data connection is possible only with wi-fi. Has any of you encountered such problems?
And last: I'm not able to install gapps provided in first post. Is anyone else affected too?
Thanks
Chris
Click to expand...
Click to collapse
Thanks, good to know! maybe next week I will give it a try and follow your advices!