{
"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"
}
Team Exodus brings you EXODUS Rom, coded by professional level developers with additional support from the community, focusing on improved versions of common features and improvements found in the open-source community while bringing new, original improvements and coding with the highest standards.
ATTENTION: Regarding 6.0 support for this device, please refer to the 2nd post!
Be rooted w/ a custom recovery (use this special recovery: http://forum.xda-developers.com/zuk-z1/orig-development/official-breadcrusts-twrp-2-8-7-0-t3217952 by me and @Breadcrust)
Download EXODUS Rom & Gapps for your device and move them to your phone
Reboot to Recovery
Wipe (Full wipe if coming from another Rom)**
Flash the Rom
Flash the Gapps**
Reboot to System
Setup and Reboot System
These directions are not necessary after the first install if you use the Exodus Updater. It can notify you of updates, download, and install them for you automatically.
**This is automated if coming from a previous Exodus build (Dirty Flashing).
EXODUS - official: http://www.exodus-developers.net/exodus-5.1/
The codename of the Zuk Z1 is "ham".
Direct download: http://exodus-developers.net/exodus-5.1/ham/
GApps: Any 5.1.x GApps of your choice
Gerrit: http://exodus-developers.net:8000
We recommend using our stock (preinstalled) kernel to use all features!
For additional support, info, and updates please join us in the official Google+ community:
https://plus.google.com/communities/106801227383087889476
Website:
http://www.exodus-developers.net/
Crowdin project:
Help us with translating to support your native language!
Thank you to all the members, contributors, and maintainers on the Exodus Team. Please
see our source for an unabridged list of contributions, authorship, and cherry-picks.
Be sure to check out Dave Kessler's Exodus Updater application in the Play Store:
https://play.google.com/store/apps/details?id=com.exodus.exodus_updater
If you would like to thank us for our hard work or help support server costs you can do so here:
MartinRo (Server hosting)
Primedirective (Team Leader / Main developer)
Some videos created by savadam (all credits to him):
XDA:DevDB Information
Exodus Android for the Zuk Z1, ROM for the Lenovo Zuk Z1
Contributors
TheCrazyLex, PrimeDirective, Raja.M, Martin_Ro
Source Code: https://github.com/TeamExodus
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: AOSP,CyanogenMod, CAF
Version Information
Status: Stable
Current Stable Version: Nightly
Stable Release Date: 2015-11-10
Beta Release Date: 2015-11-08
Created 2015-11-08
Last Updated 2015-11-10
6.0 support for Zuk Z1 Ham
Will this device get Exodus 6.0?
The problem is that no one of us owns the device and it is nearly impossible to do the bringup if no one owns the device.
However some users asked me if they can donate to me so I can buy the device and work on Exodus 6.0 for it.
The device will obviously also get improved support and more device specific patches.
I don't want to force anybody to donate, so if you have doubts, don't do it
If you really want to support my team, me and the Exodus Community you can donate HERE
Please write Additional Notes in the corresponding textfield and also whether you want the money back if the device funding is not successfull.
Thank you!
Alex
Reserved
Thanks, thanks, thanks.
Works fine for me. Wifi is now perfect. No bugs detected.
Thanks again, thank you very much.
Sorry my poor english.
Edit: Camera bug.
Good Evening Alex, can you post a Quick Tutorial to flash our special costum recovery? I want to install this ROM, but i don't have a clear idea to do this step, thanks for all Exodus Developers to bring us this ROM!
Thank you very much for this ROM!!!!
I'm testing and is a treat to regain so many options that I missed.
Thanks!! Alex
Downloading for test.
Cm themer is included?
Enviado desde mi Z1 mediante Tapatalk
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
deejaycarras said:
Good Evening Alex, can you post a Quick Tutorial to flash our special costum recovery? I want to install this ROM, but i don't have a clear idea to do this step, thanks for all Exodus Developers to bring us this ROM!
Click to expand...
Click to collapse
Sólo tienes que meterle el recovery que está adjunto y te bajas la rom y unas gapps y a flashear por twrp.
Primero antes de nada wipe factory reset, flashea y después Wipe cache / dalvik y listo
Enviado desde mi Z1 mediante Tapatalk
liver20 said:
Thanks!! Alex
Downloading for test.
Cm themer is included?
Enviado desde mi Z1 mediante Tapatalk
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
Sólo tienes que meterle el recovery que está adjunto y te bajas la rom y unas gapps y a flashear por twrp.
Primero antes de nada wipe factory reset, flashea y después Wipe cache / dalvik y listo
Enviado desde mi Z1 mediante Tapatalk
Click to expand...
Click to collapse
Yes CM Theme engine is included
deejaycarras said:
Good Evening Alex, can you post a Quick Tutorial to flash our special costum recovery? I want to install this ROM, but i don't have a clear idea to do this step, thanks for all Exodus Developers to bring us this ROM!
Click to expand...
Click to collapse
You mean a tutorial how to install twrp?
Is this currently based on CM nightlies? Are they out already?
Thanks for your work!
javirenart said:
Is this currently based on CM nightlies? Are they out already?
Thanks for your work!
Click to expand...
Click to collapse
No cm Nightlies are not out yet.
TheCrazyLex said:
No cm Nightlies are not out yet.
Click to expand...
Click to collapse
Oh okay. So what have you based this on?
Enviado desde mi Z1 mediante Tapatalk
javirenart said:
Oh okay. So what have you based this on?
Enviado desde mi Z1 mediante Tapatalk
Click to expand...
Click to collapse
CyanogenMod
TheCrazyLex said:
CyanogenMod
Click to expand...
Click to collapse
Okay I get it. hahaha
How is the device funding going on? Do you think you will get the donations needed?:angel:
javirenart said:
Okay I get it. hahaha
How is the device funding going on? Do you think you will get the donations needed?:angel:
Click to expand...
Click to collapse
Right now, I cannot say. Not much here..
However I will keep this transparent and always update you here
Tried CameraNext and also GoogleCamera and both are FC.
Other stuff from the ROM is wrking very well, as espected
Code:
E/CAM_CameraActivity( 8247): Camera error callback. error=100
E/CAM_CameraActivity( 8247): Camera Exception
E/CAM_CameraActivity( 8247): java.lang.RuntimeException: Media server died.
E/CAM_CameraActivity( 8247): at com.android.ex.camera2.portability.AndroidCameraAgentImpl$CameraHandler.onError(AndroidCameraAgentImpl.java:336)
E/CAM_CameraActivity( 8247): at android.hardware.Camera$EventHandler.handleMessage(Camera.java:1197)
E/CAM_CameraActivity( 8247): at android.os.Handler.dispatchMessage(Handler.java:102)
E/CAM_CameraActivity( 8247): at android.os.Looper.loop(Looper.java:135)
E/CAM_CameraActivity( 8247): at android.os.HandlerThread.run(HandlerThread.java:61)
D/ExtendedUtils( 320): extended extractor not needed, return default
D/NuPlayerDriver( 320): start(0xb61becc0)
I/GenericSource( 320): start
E/CAM_FatalErrorHandler( 8247): Handling Fatal Error:
E/CAM_FatalErrorHandler( 8247): java.lang.Exception
E/CAM_FatalErrorHandler( 8247): at com.android.camera.FatalErrorHandlerImpl.handleFatalError(FatalErrorHandlerImpl.java:117)
E/CAM_FatalErrorHandler( 8247): at com.android.camera.CameraActivity$11.onFatalError(CameraActivity.java:1413)
E/CAM_FatalErrorHandler( 8247): at com.android.camera.CameraActivity$11.onCameraException(CameraActivity.java:1392)
E/CAM_FatalErrorHandler( 8247): at com.android.ex.camera2.portability.CameraExceptionHandler$3.run(CameraExceptionHandler.java:103)
E/CAM_FatalErrorHandler( 8247): at android.os.Handler.handleCallback(Handler.java:739)
E/CAM_FatalErrorHandler( 8247): at android.os.Handler.dispatchMessage(Handler.java:95)
E/CAM_FatalErrorHandler( 8247): at android.os.Looper.loop(Looper.java:135)
E/CAM_FatalErrorHandler( 8247): at android.app.ActivityThread.main(ActivityThread.java:5294)
E/CAM_FatalErrorHandler( 8247): at java.lang.reflect.Method.invoke(Native Method)
E/CAM_FatalErrorHandler( 8247): at java.lang.reflect.Method.invoke(Method.java:372)
E/CAM_FatalErrorHandler( 8247): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/CAM_FatalErrorHandler( 8247): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
EDIT: Tried FV-5, OpenCamera y Lenovo SuperCamera and also stop working...
bartito said:
Tried CameraNext and also GoogleCamera and both are FC.
Other stuff from the ROM is wrking very well, as espected
Code:
E/CAM_CameraActivity( 8247): Camera error callback. error=100
E/CAM_CameraActivity( 8247): Camera Exception
E/CAM_CameraActivity( 8247): java.lang.RuntimeException: Media server died.
E/CAM_CameraActivity( 8247): at com.android.ex.camera2.portability.AndroidCameraAgentImpl$CameraHandler.onError(AndroidCameraAgentImpl.java:336)
E/CAM_CameraActivity( 8247): at android.hardware.Camera$EventHandler.handleMessage(Camera.java:1197)
E/CAM_CameraActivity( 8247): at android.os.Handler.dispatchMessage(Handler.java:102)
E/CAM_CameraActivity( 8247): at android.os.Looper.loop(Looper.java:135)
E/CAM_CameraActivity( 8247): at android.os.HandlerThread.run(HandlerThread.java:61)
D/ExtendedUtils( 320): extended extractor not needed, return default
D/NuPlayerDriver( 320): start(0xb61becc0)
I/GenericSource( 320): start
E/CAM_FatalErrorHandler( 8247): Handling Fatal Error:
E/CAM_FatalErrorHandler( 8247): java.lang.Exception
E/CAM_FatalErrorHandler( 8247): at com.android.camera.FatalErrorHandlerImpl.handleFatalError(FatalErrorHandlerImpl.java:117)
E/CAM_FatalErrorHandler( 8247): at com.android.camera.CameraActivity$11.onFatalError(CameraActivity.java:1413)
E/CAM_FatalErrorHandler( 8247): at com.android.camera.CameraActivity$11.onCameraException(CameraActivity.java:1392)
E/CAM_FatalErrorHandler( 8247): at com.android.ex.camera2.portability.CameraExceptionHandler$3.run(CameraExceptionHandler.java:103)
E/CAM_FatalErrorHandler( 8247): at android.os.Handler.handleCallback(Handler.java:739)
E/CAM_FatalErrorHandler( 8247): at android.os.Handler.dispatchMessage(Handler.java:95)
E/CAM_FatalErrorHandler( 8247): at android.os.Looper.loop(Looper.java:135)
E/CAM_FatalErrorHandler( 8247): at android.app.ActivityThread.main(ActivityThread.java:5294)
E/CAM_FatalErrorHandler( 8247): at java.lang.reflect.Method.invoke(Native Method)
E/CAM_FatalErrorHandler( 8247): at java.lang.reflect.Method.invoke(Method.java:372)
E/CAM_FatalErrorHandler( 8247): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/CAM_FatalErrorHandler( 8247): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
EDIT: Tried FV-5, OpenCamera y Lenovo SuperCamera and also stop working...
Click to expand...
Click to collapse
Ok, i've tried Cameringo Lite and seems works a little better, but i notice when resolution is lower or equal to 8MP camera works very well, but when resolution is set in 13MP camera works with low speed, seems it will hang, but works.
EDIT: Cameringo fails too, trying more camera APPs.
Otherwise, good job Alex!!!!! [emoji5] [emoji5] [emoji5]
Enviado desde mi Z1 mediante Tapatalk
deejaycarras said:
Ok, i've tried Cameringo Lite and seems works a little better, but i notice when resolution is lower or equal to 8MP camera works very well, but when resolution is set in 13MP camera works with low speed, seems it will hang, but works.
EDIT: Cameringo fails too, trying more camera APPs.
Otherwise, good job Alex!!!!! [emoji5] [emoji5] [emoji5]
Enviado desde mi Z1 mediante Tapatalk
Click to expand...
Click to collapse
I am looking into how I can resolve this issue.
Alex
Hello,
Using this ROM since yesterday.
I will post my results:
* WiFi bug is still present (expected nothing yet)
* Notifications sound bug is still present (expected nothing yet)
* Camera is unusable
* Fingerprint sensitivity seems a little lower than CMS
* Sounds after usage of TWRP dissapears until I wipe data from the phone (I need to install stock recovery) [It does not affect everyone but me]
All other stuff is working great!
Good job Alex!
Robert
bartito said:
Hello,
Using this ROM since yesterday.
I will post my results:
* WiFi bug is still present (expected nothing yet)
* Notifications sound bug is still present (expected nothing yet)
* Camera is unusable
* Fingerprint sensitivity seems a little lower than CMS
* Sounds after usage of TWRP dissapears until I wipe data from the phone (I need to install stock recovery) [It does not affect everyone but me]
All other stuff is working great!
Good job Alex!
Robert
Click to expand...
Click to collapse
Would you please elaborate the "Notifications sound bug is still present"!?
What is this bug exactly?
Related
Q&A for [ROM][CM 10.1]Samsung Galaxy Music (GT-S6010/L/12)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM 10.1]Samsung Galaxy Music (GT-S6010/L/12). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Alonso1398 said:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
So thanks to a lot of help from dhinesh77 managed to build CM for the Galaxy Music. It is almost stable, it is your choice if you use it for daily use or not (bugs below). Since it is almost stable it will be an RC release.
Thanks to:
-Cyanogenmod Team for this awesome rom
-Big thanks to dhinesh77
-pawitp's patches
-xda forum
-If someone is missing please tell me
Bugs
This are the most important bugs and the one I know so far:
-Bluetooth can only send files when it is recently turned on
-FM Radio
-Incoming sound on online calls (e.g. skype, viber...)
Requirements
You must have the CWM for the galaxy music, NOT TWRP. Post here
Also you must install cm over stock JB 4.1.X, installing from ICS 4.0.X will cause issues
Note: If after installing you have some problems about a pin unlock, try installing from a stock rom of another country
Install instructions
-Make a backup first just in case
-Wipe data/factory reset
-Wipe Cache
-Wipe Dalvik Cache on advanced
-Flash CM 10.1 for galaxy music
-Flash gapps. Link here
NOTE: If you are upgrading from a previous version of CM 10.1 you can just install it without wiping
Download link
https://www.dropbox.com/s/n72pxqvvw4inops/CM 10.1 ivoryss RC 6.zip?dl=0
Note
For those with the Galaxy Music Duos (GT-S6012) probably you will need to edit the updater-script in /META-INF/com/google/android/ and make it to match the device's name in your build.prop (it could be "ivoryss", "ivory" or "ivoryssxx". I hope that's enough for making it to work on the duos variant
NOTE: Dual sim function won't work on the duos variant, only on cm 11 releases will work
Changelog
RC6
-Fixed Offline Charging animation
RC5
-Fixed MTP
-More features to kernel
*InteractiveX governor added
*zen IO scheduler added
RC4
-Added new media_profiles.xml fixing video recording
-New features to the kernel
*Added to new governors (smartassv2 and lulzactive)
*Enabled interactive governor on the kernel
*Added two new I/O schedulers (SIO and ROW)
RC3
-New compiled build
-Fixed kernel source to work both wifi and calls
-Cleaned layout (removed torch toggle since there is no torch on Galaxy Music and removed other files)
RC2
-Replaced kernel with stock
*Fixes reboot call bug
*Wi-fi did not work anymore
RC1
-Initial realease
Source
Device tree: https://github.com/Alonso1398/android_device_samsung_ivoryss
Kernel source: https://github.com/Alonso1398/muZic_kernel_ivoryss
Click to expand...
Click to collapse
fix play store please and fix bluetooth friend
alexvzlaxda said:
fix play store please and fix bluetooth friend
Click to expand...
Click to collapse
Play store is working for me, did your flash gapps correctly? and in the future will try to fix bluetooth
rahimali said:
First of all, thank you for whatever you have done so far, it's a brilliant job!
Next, best of luck with your exam results.
Lastly, how high is the risk with the frankenstein kernel? i.e., worst comes to worst, I'll be able to flash back your CM10.1 kernel and have a working phone right? Or is there a chance of a hard brick? Could you help me with the kernel please if it's not a high risk issue? i.e., make a test kernel for me? Would like to test if that enables internet calling on the phone...
Thanks!
Click to expand...
Click to collapse
Wait, you want stock kernel on cm 10 or cm 10 kernel on stock rom?
Also I'm having issues fixing bluetooth, when I try to turn it on, phone freezes. Here is a logcat
Code:
D/AdapterServiceConfig( 4311): Adding HeadsetService
D/AdapterServiceConfig( 4311): Adding A2dpService
D/AdapterServiceConfig( 4311): Adding HidService
D/AdapterServiceConfig( 4311): Adding HealthService
D/AdapterServiceConfig( 4311): Adding PanService
D/BluetoothAdapterService( 4311): REFCOUNT: CREATED. INSTANCE_COUNT1
D/BluetoothManagerService( 1681): Message: 20
D/BluetoothManagerService( 1681): Added callback: [email protected]:true
D/BluetoothAdapterState( 4311): make
I/bluedroid( 4311): init
I/bte_conf( 4311): Attempt to load stack conf from /etc/bluetooth/bt_stack.conf
I/bluedroid( 4311): get_profile_interface socket
D/BluetoothManagerService( 1681): BluetoothServiceConnection: connected to AdapterService
D/BluetoothManagerService( 1681): Message: 40
D/BluetoothManagerService( 1681): MESSAGE_BLUETOOTH_SERVICE_CONNECTED
D/BluetoothManagerService( 1681): Calling onBluetoothServiceUp callbacks
D/BluetoothManagerService( 1681): Broadcasting onBluetoothServiceUp() to 5 receivers.
D/BluetoothAdapterService( 4311): Broadcasting updateAdapterState() to 1 receivers.
D/BluetoothBondStateMachine( 4311): make
D/BluetoothManagerService( 1681): Message: 60
D/BluetoothManagerService( 1681): MESSAGE_BLUETOOTH_STATE_CHANGE: prevState = 10, newState=11
D/BluetoothManagerService( 1681): Bluetooth State Change Intent: 10 -> 11
W/BroadcastQueue( 1681): Permission Denial: receiving Intent { act=android.bluetooth.adapter.action.STATE_CHANGED flg=0x8000010 (has extras) } to ProcessRecord{415fde68 3321:com.cleanmaster.mguard:service/u0a10076} (pid=3321, uid=10076) requires android.permission.BLUETOOTH due to sender android (uid 1000)
I/GKI_LINUX( 4311): gki_task_entry: gki_task_entry task_id=1 [BTIF] starting
D/BluetoothAdapterService(1088614272)( 4311): getState(): mAdapterProperties: [email protected]
I/ActivityManager( 1681): Start proc com.android.settings for broadcast com.android.settings/.bluetooth.DockEventReceiver: pid=4330 uid=1000 gids={41000, 1015, 1028, 3002, 3001, 3003, 3007}
D/BluetoothHeadset( 2079): Proxy object connected
D/BluetoothHeadset( 1681): Proxy object connected
D/BluetoothAdapterService(1088614272)( 4311): getState(): mAdapterProperties: [email protected]
D/HeadsetService( 4311): Received start request. Starting profile...
D/BluetoothHeadset( 2079): Proxy object connected
I/BluetoothHeadsetServiceJni( 4311): classInitNative: succeeds
I/BluetoothBondStateMachine( 4311): StableState(): Entering Off State
D/HeadsetStateMachine( 4311): make
D/BluetoothManagerService( 1681): Bluetooth Adapter name changed to Luis
D/BluetoothManagerService( 1681): Stored Bluetooth name: Luis
I/bluedroid( 4311): get_profile_interface handsfree
E/bt-btif ( 4311): btif_enable_service: current services:0x40
D/BluetoothA2dp( 1681): Proxy object connected
D/BluetoothAdapterService(1088614272)( 4311): getState(): mAdapterProperties: [email protected]
D/A2dpService( 4311): Received start request. Starting profile...
I/BluetoothA2dpServiceJni( 4311): classInitNative: succeeds
D/A2dpStateMachine( 4311): make
I/bluedroid( 4311): get_profile_interface a2dp
I/GKI_LINUX( 4311): gki_task_entry: gki_task_entry task_id=2 [A2DP-MEDIA] starting
E/bt-btif ( 4311): btif_enable_service: current services:0x40040
I/BluetoothHidServiceJni( 4311): classInitNative: succeeds
D/A2dpStateMachine( 4311): Enter Disconnected: -2
D/HidService( 4311): Received start request. Starting profile...
I/bluedroid( 4311): get_profile_interface hidhost
E/bt-btif ( 4311): btif_enable_service: current services:0x140040
I/BluetoothHealthServiceJni( 4311): classInitNative: succeeds
D/HealthService( 4311): Received start request. Starting profile...
I/bluedroid( 4311): get_profile_interface health
I/BluetoothPanServiceJni( 4311): classInitNative(L105): succeeds
D/BluetoothPan( 1681): BluetoothPAN Proxy object connected
D/PanService( 4311): Received start request. Starting profile...
D/BluetoothPanServiceJni( 4311): initializeNative(L110): pan
I/bluedroid( 4311): get_profile_interface pan
D/HeadsetPhoneState( 4311): sendDeviceStateChanged. mService=0 mSignal=0 mRoam=0 mBatteryCharge=2
D/BluetoothAdapterService( 4311): Profile still not running:com.android.bluetooth.hdp.HealthService
D/BluetoothAdapterService( 4311): Profile still not running:com.android.bluetooth.hdp.HealthService
D/BluetoothAdapterService( 4311): Profile still not running:com.android.bluetooth.hdp.HealthService
D/BluetoothAdapterService( 4311): Profile still not running:com.android.bluetooth.pan.PanService
I/bluedroid( 4311): enable
I/bt_hci_bdroid( 4311): init
I/bt_vendor( 4311): init
I/bt_vnd_conf( 4311): Attempt to load conf from /etc/bluetooth/bt_vendor.conf
I/bt_vnd_conf( 4311): vnd_load_conf file >/etc/bluetooth/bt_vendor.conf< not found
I/bt_hci_bdroid( 4311): bt_hc_worker_thread started
I/bt_userial_vendor( 4311): userial vendor open: opening /dev/ttyS0
Any ideas?
Alonso1398 said:
Wait, you want stock kernel on cm 10 or cm 10 kernel on stock rom?
Click to expand...
Click to collapse
actually, i was thinking maybe we could try if using the stock jb4.1.2 kernel with your cm10.1 rom and see if we can enable internet calling and dual sim support. possible?
I have a little problem
Good I'm new , I'm from Venezuela excuse me for my bad English ... I have problems with unlocking the SIM everything works fine except me that my phone is a GT- S6010 ... I can help ?
I just installed the ROM on my Galaxy GT-S6010L Music and ... surprise! It does not recognize the chip ... emergency calls only? I came so the rom?
Exactly
lcorredorh said:
Good I'm new , I'm from Venezuela excuse me for my bad English ... I have problems with unlocking the SIM everything works fine except me that my phone is a GT- S6010 ... I can help ?
Click to expand...
Click to collapse
Tengo el mismo problema, según dice el autor intenta instalar CM desde una stock ROM 4.1.2, y que sino funciona que intentes con otra de otro país, por allí leí que este error se soluciona si primero instalas la ROM de Panamá, Intentare hacer eso a ver si funciona.
Tampoco me funciono lo de Panama...
lcorredorh said:
Tampoco me funciono lo de Panama...
Click to expand...
Click to collapse
He pasado todo el dia buscando alguna solucion pero no he conseguido solucion alguna , tenia pensado bajar varios stock rom e ir probando con cada una de ellas a ver si el problema se soluciona, es una lastima que tenga este problema porque la rom esta de maravila..
I'm trying to install the recovery by Odin with a img convert to md5 , be giving more failure the system yourself in download mode ( odin mode) , my model is the Brazilian 6012B android 4.1.2
DeLLeTo said:
I'm trying to install the recovery by Odin with a img convert to md5 , be giving more failure the system yourself in download mode ( odin mode) , my model is the Brazilian 6012B android 4.1.2
Click to expand...
Click to collapse
you use rashr or flashify to flash recovery
@Alonso1398, any chance of getting dual sims to work?
you must port galaxy pocket 2 or young 2 roms they will work well on galaxy music as i know the ram and cpu and size of the screen is same
oryou can start using cyanogen mod 12 i think its better than cyanogen mod 10 or 11 the dous may work too
rahimali said:
you use rashr or flashify to flash recovery
@Alonso1398, any chance of getting dual sims to work?
Click to expand...
Click to collapse
I don't think so only cm 11 is capable of getting dual sim
armanote said:
you must port galaxy pocket 2 or young 2 roms they will work well on galaxy music as i know the ram and cpu and size of the screen is same
oryou can start using cyanogen mod 12 i think its better than cyanogen mod 10 or 11 the dous may work too
Click to expand...
Click to collapse
I think the young 2 and pocket 2 has different cpu so I don't think I can port from them. And I know about cm 12 and lollipop but remember I don't know too much of programing so I can't bring lollipop for now, I'm porting from pocket neo's cm 10.1 and cm 11. If it gets cm 12 I might port it
Alonso1398 said:
I don't think so only cm 11 is capable of getting dual sim
I think the young 2 and pocket 2 has different cpu so I don't think I can port from them. And I know about cm 12 and lollipop but remember I don't know too much of programing so I can't bring lollipop for now, I'm porting from pocket neo's cm 10.1 and cm 11. If it gets cm 12 I might port it
Click to expand...
Click to collapse
Maybe you could drop kitkat altogether and work on lollipop instead
rahimali said:
Maybe you could drop kitkat altogether and work on lollipop instead
Click to expand...
Click to collapse
lol not yet, I think cm 12 is still in alpha state so I will wait a little bit more, however it seems that pocket neo got cm 12 so in a long future I will try to port it.
Still no progress with bluetooth in cm 10.1 but in cm 11 got egl and wifi working
Please
Hey installing the ROM I lock the sim, I do not quite understand how to solve what if they say as they solve, Please
not working on samsung galaxy music duos 4.0.4 firmware
sir i m using galaxy music duos whenever i flash cm10.1 it succesfully flash but after words its jst reeboots itself again again.. i m not getting is it because i m on ics ..?
willy94inh said:
He pasado todo el dia buscando alguna solucion pero no he conseguido solucion alguna , tenia pensado bajar varios stock rom e ir probando con cada una de ellas a ver si el problema se soluciona, es una lastima que tenga este problema porque la rom esta de maravila..
Click to expand...
Click to collapse
I'm sorry about those problems (I don't think I can solve it) an user told me that cm 11 didn't had that bug and yesterday released the first RC so it can be used for daily use
In spanish :Lo siento mucho acerca esos problemas (no creo que los pueda resolver) un usuario me dijo que en cm 11 no tuvo ese problema y ayer saqué la primera RC así que se puede usar a diario
jhumpi said:
sir i m using galaxy music duos whenever i flash cm10.1 it succesfully flash but after words its jst reeboots itself again again.. i m not getting is it because i m on ics ..?
Click to expand...
Click to collapse
Yes, you need to install it on stock jb 4.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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
.
Check out the full feature list here
WHAT IS WORKING?
WiFi
Bluetooth
RIL (single sim support only)
Sensors
GPS
Camera
Leds
Buttons
Audio
Video
Camcorder
WHAT IS NOT WORKING?
Nothing .....!! Or you tell me.....!!!
Installation Instructions
Download the latest build
Wipe data / Factory reset
Wipe cache
Wipe dalvik cache
Flash it using ClockworkMod recovery or TWRP
Flash Gapps
Flash Addons
Reboot
Enjoy
DOWNLOADS
Unofficial Builds
Slim Gapps
SOURCES:https://github.com/YU-YUREKA
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
Slimkat for Yureka, ROM for the YU Yureka
Contributors
sooorajjj, @sufoalmighty [For mirror links -available in 3rd post] , @Santhosh M and @faux123 [ for awesome kernel patches ] , Official CM team and Slim team
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Yureka
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-01-20
Created 2015-01-17
Last Updated 2015-01-20
NOTE: this is not stable for daily use
i do not recommend any one to flash this
this is just initial test build
EDIT : Stable for daily use
Thanks to @Santhosh M @faux123 for kernel commits : this is his kernel thread please support him and thank him here
SCREENSHOTS
CHANGELOG*"UNOFFICIAL-BUILD-1"
Initial TRY(to get slimkat - booting )
Fixed battery capacity bug
*"UNOFFICIAL-BUILD-2"
fix up boot.img and permissions
Audio bug is caused bcs of missing hal libs - still no fix........ trying
DT2W patches failed to compile will fix in next build
*"UNOFFICIAL-BUILD-3" -Mirror --Mirror2
fixed audio
fixed video
fixed Camcorder
*"UNOFFICIAL-BUILD-4" -Mirror --Mirror2
Build with custom toolchain linario linaro-4.9-14.06
And lots of kernel patches
Thanks, Flashing!
EDIT: tested, so smooth camera isnt as good as stock, sim 2 doesnt work at all
Great work mate! :good:
1st rom for YU thanks bro.
sufoalmighty said:
Thanks, Flashing!
EDIT: tested, so smooth camera isnt as good as stock, sim 2 doesnt work at all
Click to expand...
Click to collapse
thanks for testing
TheStrix said:
Great work mate! :good:
Click to expand...
Click to collapse
Samuel117 said:
1st rom for YU thanks bro.
Click to expand...
Click to collapse
thanks guys for support
@DooMLoRD @championswimmer
please take a look at these logs
audio hal issue - i think its because the audio effects and much more implementations by cm
http://paste.ubuntu.com/9770340/
http://paste.ubuntu.com/9770344/
http://paste.ubuntu.com/9763980/
Code:
I/MediaFocusControl( 827): AudioFocus requestAudioFocus() from [email protected]
V/Avrcp ( 2319): New genId = 9, clearing = 1
E/EffectProxy( 248): EffectCreate() could not get the sub effects
W/EffectsFactory( 248): EffectCreate() library proxy: could not create fx Qualcomm Bass Boost, error -22
E/AudioEffect( 4710): set(): AudioFlinger could not create effect, status: -22
E/AudioEffects-JNI( 4710): AudioEffect initCheck failed -4
E/AudioEffect-JAVA( 4710): Error code -4 when initializing AudioEffect.
D/AndroidRuntime( 4710): Shutting down VM
E/AndroidRuntime( 4710): FATAL EXCEPTION: main
E/AndroidRuntime( 4710): Process: com.android.gallery3d, PID: 4710
E/AndroidRuntime( 4710): java.lang.RuntimeException: Unable to resume activity {com.android.gallery3d/com.android.gallery3d.app.MovieActivity}: java.lang.IllegalArgumentException: Effect type: 0634f220-ddd4-11db-a0fc-0002a5d5c51b not supported.
E/AndroidRuntime( 4710): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2777)
E/AndroidRuntime( 4710): at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2806)
E/AndroidRuntime( 4710): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2241)
E/AndroidRuntime( 4710): at android.app.ActivityThread.access$800(ActivityThread.java:138)
E/AndroidRuntime( 4710): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1199)
E/AndroidRuntime( 4710): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 4710): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 4710): at android.app.ActivityThread.main(ActivityThread.java:5034)
E/AndroidRuntime( 4710): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 4710): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
E/AndroidRuntime( 4710): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
E/AndroidRuntime( 4710): Caused by: java.lang.IllegalArgumentException: Effect type: 0634f220-ddd4-11db-a0fc-0002a5d5c51b not supported.
E/AndroidRuntime( 4710): at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:405)
E/AndroidRuntime( 4710): at android.media.audiofx.BassBoost.<init>(BassBoost.java:101)
E/AndroidRuntime( 4710): at com.android.gallery3d.app.MovieActivity.initEffects(MovieActivity.java:393)
E/AndroidRuntime( 4710): at com.android.gallery3d.app.MovieActivity.onResume(MovieActivity.java:504)
E/AndroidRuntime( 4710): at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1192)
E/AndroidRuntime( 4710): at android.app.Activity.performResume(Activity.java:5320)
E/AndroidRuntime( 4710): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2767)
E/AndroidRuntime( 4710): ... 10 more
W/ActivityManager( 827): Force finishing activity com.android.gallery3d/.app.MovieActivity
W/ActivityManager( 827): Force finishing activity com.android.gallery3d/.app.GalleryActivity
W/ActivityManager( 827): Activity pause timeout for ActivityRecord{6504dd28 u0 com.android.gallery3d/.app.MovieActivity t8 f}
I/Timeline( 2051): Timeline: Activity_idle id: [email protected] time:835130
I/Timeline( 827): Timeline: Activity_windows_visible id: ActivityRecord{64ffaa90 u0 com.slim.slimlauncher/.Launcher t1} time:835454
I/MSM-irqbalance( 239): Decided to move IRQ130 from CPU5 to CPU6
W/ActivityManager( 827): Activity destroy timeout for ActivityRecord{6534bac0 u0 com.android.gallery3d/.app.GalleryActivity t8 f}
W/ActivityManager( 827): Activity destroy timeout for ActivityRecord{6504dd28 u0 com.android.gallery3d/.app.MovieActivity t8 f}
I/MSM-irqbalance( 239): Decided to move IRQ131 from CPU5 to CPU6
Code:
D/AudioPolicyManagerBase( 248): getOutput() device 2, stream 1, samplingRate 0, format 0, channelMask 3, flags 0
D/AudioPolicyManagerBase( 248): getOutput() returns output 2
D/AudioPolicyManagerBase( 248): getOutput() device 2, stream 1, samplingRate 0, format 0, channelMask 3, flags 0
D/AudioPolicyManagerBase( 248): getOutput() returns output 2
D/AudioPolicyManagerBase( 248): getOutput() device 2, stream 1, samplingRate 48000, format 1, channelMask 3, flags 4
D/AudioPolicyManagerBase( 248): getOutput() returns output 3
W/AudioTrack( 827): AUDIO_OUTPUT_FLAG_FAST denied by client due to mismatching sample rate (48000 vs 44100)
D/AudioFlinger( 248): start(4099), calling pid 827 session 52
D/AudioFlinger( 248): ? => ACTIVE (4099) on thread 0xb87083f0
I/QCOM PowerHAL( 248): Processing audio hint. Metadata: state=1
D/AudioPolicyManagerBase( 248): startOutput() output 3, stream 1, session 52
I/ActivityManager( 827): START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from pid 1892
D/SubSettings( 1892): Launching fragment com.android.settings.deviceinfo.Memory
here is the vendor blobs iam using
https://github.com/YU-YUREKA/proprietary_vendor_yu
any kind of help is appreciated
thank you
sooraj
video cant be played ???
---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------
can u give me link of stock rom
op updated new build is up for download
-------changes------
*"UNOFFICIAL-BUILD-2"
fix up boot.img and permissions
Audio bug is caused bcs of missing hal libs - still no fix........ trying
DT2W patches failed to compile will fix in next build
Kanth's said:
video cant be played ???
---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------
can u give me link of stock rom
Click to expand...
Click to collapse
yes video can be played but not in gallery youtube wrks
and sorry i dont have link to stok rom
I would recommend this to move to android development
vishal_android freak said:
I would recommend this to move to android development
Click to expand...
Click to collapse
But why .?...!!! its completely a build from source and i have met all GPL requirements
sooorajjj
Thanks for the update version 3 for stable release
ela1103 said:
sooorajjj
Thanks for the update version 3 for stable release
Click to expand...
Click to collapse
you are welcome
the build will be up soon .....!
uploading on slow connection
sooorajjj
use the mediafire site to upload and download .because the speed is stable
ela1103 said:
sooorajjj
use the mediafire site to upload and download .because the speed is stable
Click to expand...
Click to collapse
sorry i cant use mediafire ........ but maybe someone can mirror the links
BUILD is UP
Is it possible to port it to coolpad f2 or install this one on this smartphone?
albin88 said:
Is it possible to port it to coolpad f2 or install this one on this smartphone?
Click to expand...
Click to collapse
Do not install this build directly to coolpad f2
you need to replace boot.img so yes porting is posssible
Just replace boot.img or something more? Could you port it or this is not so simple?
albin88 said:
Just replace boot.img or something more? Could you port it or this is not so simple?
Click to expand...
Click to collapse
do you have recovery installed to flash this on your coolpad f2 ?
if yes then make a backup and try try flashing the rom as it is if it doesn’t boot dont worry it wont brick your device .....! just go back to recovery and restore your backup ............ try this then report ....
This ROM has gone "Alpha" and is basically ready for daily use https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571 or you could also check ResurrectionRemix at https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
See the following post for the current status of this experimental build.
https://forum.xda-developers.com/showpost.php?p=74272802&postcount=59
all the below is regarding previous build attempts
DO NOT FLASH GAPPS!
Make a nandroid (you will definitely be going back) And remember, a nandroid is NOT 100%! if you don't understand this, maybe trying this is not for you.
Flash the ZIP
It is unrooted, so I personally flash Magisk v12 (I have the zip and know its working). I also flash UnSu and Busybox remover
DO NOT FLASH GAPPS!
Reboot
Install the Magisk Manager (if you went down this path for root)
This is an experimental build of crDroid 7.1.2
The good
It's crDroid!
It's Nougat!
It Builds
It Boots!:highfive:
It has all the eyecandy!:angel:
It feels really "snappy"
The bad
If you flash Gapps it falls to pieces in a never ending cycle of crashes!:crying:
It is buggy even without GApps
My Hopes:
People will flash this, get some logs and maybe someone with more knowledge (maybe the xt897 LOS device maintainers?) will be able to decipher the logs and determine whats missing. Maybe someone here has a direct line to one of the maintainers of the xt897 LineageOS?
How I built it:
Set up a virtual Box (on Win7 64b) to build Lineage OS 14.1 (followed their instructions)
Source: https://github.com/crdroidandroid/android -b 7.1
I used a working device tree (ie local manifest) from my working LineageOS 14.1 Build machine (see attached) for an XT897 (with the touch drivers for an XT907)
Basically, I have done no "magic" here, it all just kinda worked. up to a point as its pretty buggy. BUT IT BOOTS!
I also have a ResurrectionRemix 7.1.2 I will also upload.
Almost forgot, flash this at your own risk and i take no responsibility for what happens to your device.
DiamondJohn said:
DO NOT FLASH GAPPS!
Click to expand...
Click to collapse
Since GApps seem to be the only limiting factor, did you try the various available flavors of GApps?
Also, there's one more alternate to GApps, which is the microg project. Did you try that instead? There's an unofficial flashable installer available here but that page also has links to the various components if you wish to install those manually...
rahimali said:
Since GApps seem to be the only limiting factor, did you try the various available flavors of GApps?
Also, there's one more alternate to GApps, which is the microg project. Did you try that instead? There's an unofficial flashable installer available here but that page also has links to the various components if you wish to install those manually...
Click to expand...
Click to collapse
I tried Open (Pico) & Beans from memory.
I think the real answer will be to look into the logs. The very first build I did I got ADB over WiFi turned on before it all went bad, so have a catlog of the SystemUI crashes, but it was an earlier build , and its from ResurectionRemix
I think this is the smoking gun:
Code:
07-19 20:14:36.665 5929 5929 D AndroidRuntime: Shutting down VM
07-19 20:14:36.669 5929 5929 E AndroidRuntime: FATAL EXCEPTION: main
07-19 20:14:36.669 5929 5929 E AndroidRuntime: Process: com.android.systemui, PID: 5929
[COLOR="Red"][B]07-19 20:14:36.669 5929 5929 E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/android/keyguard/R$bool;
[/B][/COLOR]07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.keyguard.KeyguardUpdateMonitor.shouldListenForFingerprint(KeyguardUpdateMonitor.java:1199)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.keyguard.KeyguardUpdateMonitor.updateFingerprintListeningState(KeyguardUpdateMonitor.java:1186)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.keyguard.KeyguardUpdateMonitor.<init>(KeyguardUpdateMonitor.java:1177)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.keyguard.KeyguardUpdateMonitor.getInstance(KeyguardUpdateMonitor.java:993)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.systemui.keyguard.KeyguardViewMediator.setupLocked(KeyguardViewMediator.java:683)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.systemui.keyguard.KeyguardViewMediator.start(KeyguardViewMediator.java:735)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.systemui.SystemUIApplication.startServicesIfNeeded(SystemUIApplication.java:180)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.systemui.SystemUIApplication.startServicesIfNeeded(SystemUIApplication.java:134)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.systemui.keyguard.KeyguardService.onCreate(KeyguardService.java:45)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3231)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.app.ActivityThread.-wrap5(ActivityThread.java)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1597)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6236)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.keyguard.R$bool" on path: DexPathList[[zip file "/system/priv-app/SystemUI/SystemUI.apk"],nativeLibraryDirectories=[/system/priv-app/SystemUI/lib/arm, /system/lib, /vendor/lib, /system/lib, /vendor/lib]]
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:380)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
07-19 20:14:36.669 5929 5929 E AndroidRuntime: ... 18 more
07-19 20:14:36.672 2801 3134 W ActivityManager: Process com.android.systemui has crashed too many times: killing!
07-19 20:14:36.673 2801 3134 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:877 com.android.server.am.AppErrors.crashApplicationInner:375 com.android.server.am.AppErrors.crashApplication:309 com.android.server.am.ActivityManagerService.handleApplicationCrashInner:13757 com.android.server.am.ActivityManagerService.handleApplicationCrash:13739
wierd, I just reflashed the ROM and it wasn't anywhere near as stable as it was the first time I flashed it
DiamondJohn said:
wierd, I just reflashed the ROM and it wasn't anywhere near as stable as it was the first time I flashed it
Click to expand...
Click to collapse
I took a big batch of logs, read them (as much as you can with that amount of crashes), did some MAJOR changes (but "impolite" and took some major shortcuts though not so quick to actually do), and now its a LOT more stable, and I even managed to install and boot with GApps, connect to the market and download a couple of apps. :highfive::victory: But don't get me wrong, it still crashes like a &@%#$
ie there are still "some" force closes
I'm moving off of this one (ie crDroid) and give ResurrectionRemix a similar "attack " :fingers-crossed: On previous attempts/builds it acted the same as crDroid, but much worse.
But most importantly, my phone is on the fritz and I think (ie hope thats it's only:fingers-crossed the recovery image is corrupt
{
"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"
}
i flashed crrdroid for the xt907 and first boot it works like a charm but when u reboot it it goes bonkers and endless force closes
i hope u can get this stable because i have crdroid installed on all of my devices my favorite nougat rom
I hope someone can keep the development going for this ROM for the xt907
my last build available in post #3 that I managed to get to work with GApps / Google play
hmmm... I'm giving it another go to get some logs and it actually seems MORE stable after a few wipes of dalvik and cache...
Can't install apps package installer force closes as well as the keyboard ?
Trey n said:
Can't install apps package installer force closes as well as the keyboard ?
Click to expand...
Click to collapse
Tell me something I dont know!
I have found its a bit of a random number generator, in that sometimes I flash and the FC's are MANY times less and others much more. But generally speaking, the faster you set the device up, the more chance you have. Also, when it starts to fail, go to recovery and clean cache and dalvik. Also delete /system/priv-app/OmniSwitch & /syatem/app/NFC/
I kicked off a new build and flashed it. As part of the build, I undid my "hacky" changes which seemed to improve stability (orig didnt allow GApps), and refreshed all crDroid code to source. I found that the new build was almost as stable as my modified build. ie as crDroid fixes bugs for their official devices, our unofficial build inherits these fixes and also becomes more stable :highfive:. So, hopefully as their builds become more mature, we may end with a stable build as well. This state of affairs (ie pure crDroid code) is the best situation / goal.
I also trued flashing (and building) one of their official devices (a Nexus 5 / hammerhead). I found that there were a number of issues even in the official builds. For example, I found that OmniSwitch caused a number of force closes in my build. In the official Nexus 5 build, although it didnt force close, it didn't actually work. ie there is work to be done in Omniswitch, which we will inherit. I also found that the official build din't have working Lockscreen album art nor music visualiser. So there is clearly a lot of coding ahead for crDroid; which again, we will inherit.
Also the more I think about it, we are more stable without GApps, and its nowhere near a daily yet, so I am seeing it more and more as a preview / test that we may have a very customizable Nougat ROM for our phones (in the future :fingers-crossed
I also noriced that for our screen resolution, the code falls back to the old B/W bootanimiation instead of the newer one. That wont do for my builds in the future
I would suggest that if anyone is really interested to see this ROM "running" and its features, then do not flash GApps; its simply a preview of what is hopefully to come.
On a side, does anyone know of a free, non registration, low advertising, fast to upload(the ones i found take 4Hrs to upload!) hosting website I can post future builds onto?
I think I will also generate a pure xt897 build to hopefully garner some interest by other devs, as the xt897 is an official LineageOS device, which is the vendor and device tree I am using to build crDroid (and ResurectionRemic and possibly other LOS based custom ROMs)
DiamondJohn said:
Tell me something I dont know!
I have found its a bit of a random number generator, in that sometimes I flash and the FC's are MANY times less and others much more. But generally speaking, the faster you set the device up, the more chance you have. Also, when it starts to fail, go to recovery and clean cache and dalvik. Also delete /system/priv-app/OmniSwitch & /syatem/app/NFC/
I kicked off a new build and flashed it. As part of the build, I undid my "hacky" changes which seemed to improve stability (orig didnt allow GApps), and refreshed all crDroid code to source. I found that the new build was almost as stable as my modified build. ie as crDroid fixes bugs for their official devices, our unofficial build inherits these fixes and also becomes more stable :highfive:. So, hopefully as their builds become more mature, we may end with a stable build as well. This state of affairs (ie pure crDroid code) is the best situation / goal.
I also trued flashing (and building) one of their official devices (a Nexus 5 / hammerhead). I found that there were a number of issues even in the official builds. For example, I found that OmniSwitch caused a number of force closes in my build. In the official Nexus 5 build, although it didnt force close, it didn't actually work. ie there is work to be done in Omniswitch, which we will inherit. I also found that the official build din't have working Lockscreen album art nor music visualiser. So there is clearly a lot of coding ahead for crDroid; which again, we will inherit.
Also the more I think about it, we are more stable without GApps, and its nowhere near a daily yet, so I am seeing it more and more as a preview / test that we may have a very customizable Nougat ROM for our phones (in the future :fingers-crossed
I also noriced that for our screen resolution, the code falls back to the old B/W bootanimiation instead of the newer one. That wont do for my builds in the future
I would suggest that if anyone is really interested to see this ROM "running" and its features, then do not flash GApps; its simply a preview of what is hopefully to come.
On a side, does anyone know of a free, non registration, low advertising, fast to upload(the ones i found take 4Hrs to upload!) hosting website I can post future builds onto?
I think I will also generate a pure xt897 build to hopefully garner some interest by other devs, as the xt897 is an official LineageOS device, which is the vendor and device tree I am using to build crDroid (and ResurectionRemic and possibly other LOS based custom ROMs)
Click to expand...
Click to collapse
AWESOME time will tell
and i have noticed that bootanimation too and i hate it i love the new one
and u could upload it to ur google drive and share the file ..........
Trey n said:
AWESOME time will tell
and i have noticed that bootanimation too and i hate it i love the new one
and u could upload it to ur google drive and share the file ..........
Click to expand...
Click to collapse
Google drive not an option. Any other ideas?
DiamondJohn said:
Google drive not an option. Any other ideas?
Click to expand...
Click to collapse
Y not?
Onedrive
Dropbox
Mediafire
Mega
also see the second half of this post https://forum.xda-developers.com/showpost.php?p=73211646&postcount=79
I also just found the following post of a user having what appears to be the exact same issues with LineageOS 14.1, when they install GApps
https://forum.xda-developers.com/droid-razr-m/development/lineage-os-xt907jbbl-t3577746/post72841480
Its a pity they dont have an xt897 so that they could post an issue/bug directly with LineageOS
Bad news all I had a chance to flash a build and actually take the logs, ie on top of all the logs you guys posted... NOT!
Anyway, in short, we are getting "GPU Page Faults" in the kernel. The GPU is Graphics Processing Unit, which would explain the systemUI crashes. The bad news is that I looked at our kernel code and compared it to another device which does work, and our kernel code is way behind. eg hammerhead code file on the line that logs the error is 2000 lines, ours is only 1000 lines.
I tried slowly updating more and more of our kernel, but each file I brought up to newer code triggered a dependency on another 2 files, and that file triggered a dependency on another few files. as you can imaging it got out of hand very quickly.
So, unless LineageOS does some major changes to their kernel, I don't think we are going to be running a heavily customised ROM too soon.:crying:
I also tried AICP just in case it was compatible with our "old" kernel, but no.All nougat of course,
I also have tried ResruectionRemix, also no.
Also tried DirtyUnicorns, which is an AOSP based ROM (instead of LiineageOS based like the rest) and that also has kernel issues.It doesn't even show the boot animation. Boot loop All of these require mods to make them compatible with their specific build process ie time :angel
I have compiled and have a working ResurectionRemix marshmallow.:good:
I have spent a lot of time trying to update our kernel, but failed every time or just got overwhelmed with the amount of change required
Lineage does do minor fixes to their Kernel, but most I have seen have been stability around the file system and not the display/GPU; where our problem is.
Additionally, the kernel code is shared between JBBL and KKBL, so I very much doubt we would have any better success with a KKBL ROM.
Why not stick to MM ROMs for now? Could you try and build a few for KKBL and/or JBBL? MM should be good enough for now on these devices and building these should give you the necessary exposure and experience to move ahead to N in the future. Just my thoughts tho m not a dev
DiamondJohn said:
I have compiled and have a working ResurectionRemix marshmallow.:good:
Click to expand...
Click to collapse
And where might I be able to obtain this?
rahimali said:
Why not stick to MM ROMs for now? Could you try and build a few for KKBL and/or JBBL? MM should be good enough for now on these devices and building these should give you the necessary exposure and experience to move ahead to N in the future. Just my thoughts tho m not a dev
Click to expand...
Click to collapse
Because Nougat is newer! Building M will not give the depth of experience needed to rebuild the kernel.
I am currently running as my daily, a custom build of LOS 13.0 (with a heap of Xposed modules). The custom build is basically a de-bloated MM with the Nougat Kernel overclocked to 1.98GHz. I compiled a RR marshmallow (with the OC'd N kernel), but during my install I noticed it had a bug whereby all my restored messages returned to being unread after every reboot. Should be an easy fix, but still a fix to be built and tested. The idea of compiling RR was to remove the need for Xposed.
After this experience, I realised that the LOS MM ROM with Xposed was pretty good, until I get N running...
NB: LOS13 has not had many code changes since they switched to Nougat. Hence my use of the Nougat kernel AND the fact their official xt897 builds should be pretty close to mine (apart from the kernel & OC)
I am guessing that noone rememebrs or tried the following. But, if you flashed the ROM and GApps, and then when it booted, NOT TOUCH the screen, did it fail / crash?
I ask because I have been working on trying to update the kernel, and after many many MANY attempts, I got one to build , flash and boot, but the touch screen drivers are not right, so the touchscreen does not work. But there is also not any force closes popping up. So I am wondering if I have solved the force closes or if it takes touching the screen to trigger their start?
Hi
OK guys. I had missed the information.
Our G5s seems to be ready to support customized ROMS :
androidpolice.com/2017/10/12/motorola-releases-kernel-source-code-moto-g5s
techdroider.com/2017/10/moto-g5s-kernel-source-code-released.html
(sorry for links)
kernel source montana > https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPP26.102-41
Pardon me if it is a wrong thread to ask this question. If it is, moderator please delete this post.
I don't see any custom ROM development happening for this device. May be I am not aware of. Or May be it is very early to expect a custom ROM. I heard that Moto G5 and G5s has same technical specification. Would I be able to flash a G5 custom rom on G5s with a little bit of tweak in build.prop (like device_name, etc)?
Thanks
Kalyan
Hello, you can try, but I do not think it works, but you will also have to modify the updater script.
I do not think it works either, but if you try it and if it works, thank you for telling us.
lohanbarth said:
Hello, you can try, but I do not think it works, but you will also have to modify the updater script.
Click to expand...
Click to collapse
Thanks for the response. I haven't rooted my device yet. I understand that would void device warranty status. I am just waiting for the OREO update to happen. It seems OREO has in-built theme support (At least that's what I read in various articles).
Couple of questions. Suppose if I unlock boot loader; play around with installing G5 custom roms and later on if I relock boot loader, would I get OTA updates?
Additionally, to the minimum I need to know the partition/blocks layout to verify with G5 updater script. Does anyone know partition/blocks layout of G5s?
Thanks
Kalyan
hello, I always unlock my motorola and I always received the updates, and if you do not receive it, there will be the rom to install the fastboot
lohanbarth said:
hello, I always unlock my motorola and I always received the updates, and if you do not receive it, there will be the rom to install the fastboot
Click to expand...
Click to collapse
Hi all, I am interested in building a ROM for this device. But as I am new to this, I don't know where to start. To the minimum, I need device_tree and vendor_tree for the device. I searched internet and went through various github repositories, but I couldn't find anything for MONTANA device.
All I found is an empty repository here https://github.com/moto8937/android_device_motorola_montana
Can anyone help me?
Thanks in advance.
Regards
KS
I suppose repo will be filled as soon as scripts for montana will be ready; maybe in next few days/weeks.
I am also interested in a ROM. AOSP or AOSP Extended would be nice.
I have much experience with Linux, bootloaders and low-level stuff. But no experience
with building Android (can't be so hard). If someone is making a ROM I can help if needed.
But I guess we must wait for source code.
janhieber said:
I am also interested in a ROM. AOSP or AOSP Extended would be nice.
I have much experience with Linux, bootloaders and low-level stuff. But no experience
with building Android (can't be so hard). If someone is making a ROM I can help if needed.
But I guess we must wait for source code.
Click to expand...
Click to collapse
Hello, normally squid2 work to get out lineageOS 15, so I think what should not be coming out soon.
lohanbarth said:
Hello, normally squid2 work to get out lineageOS 15, so I think what should not be coming out soon.
Click to expand...
Click to collapse
I am able to build a Resurrection Remix 5.8.5 custom rom using CEDRIC device code.
1) I downloaded android_device_motorola_cedric, android_vendor_motorola_cedric and android_kernel_motorola_msm8937 repositories as ZIP files from https://github.com/moto8937.
2) I changed all files in sub-directories that has 'cedric' in its name to 'montana'.
3) Replaced all file contents that had 'cedric' with 'montana'.
4) Pulled in RR code base from its GIT repository using REPO tool. I followed the instructions provided in https://github.com/ResurrectionRemix/platform_manifest
5) Copied the modified device, vendor and kernel files to appropriate directory within RR directory (~/RR/kernel/motorola/msm8937, ~/RR/device/motorola/montana and ~/RR/vendor/motorola/montana).
6) Started a brunch montana. Failed after 50% because of missing piece of code related to qcom dtbtool. So I downloaded qcom_common repository from https://github.com/LineageOS/android_device_qcom_common and placed the contents under ~/RR/device/qcom/common.
7) Started brunch montana again. Completed the build after 8 hours.
8) Took a TWRP backup of stock rom and flashed RR build.
9) Flash went through and device started without issues.
10) Now RIL, WIFI, Bluetooth, Tethering, Mobile Data, Dual SIM, etc works.
11) SOUND NOT WORKING. NO SOUND AT ALL, as if speakers are dead. I can make a call and receive a call. But I cannot hear other party. Microphone works.
12) SENSORS are not working. Like autorotate, proximity, etc.
13) It was beautiful to see 7.1.2 Nougat with October 2017 Security Patch.
----
14) Then I noticed that kernel code in https://github.com/moto8937/android_kernel_motorola_msm8937/tree/cm-14.1/arch/arm/configs already has a file called montana_defconfig. I compared that with cedric_defconfig. Both are different. The build process uses montana_defconfig by default, but the values in it are not valid. At least that is my assumption.
15) So now I renamed montana_defconfig to montana_defconfig.bak. Took a copy of cedric_defconfig and renamed the copy to montana_defconfig.
15) Tomorrow I would rebuild again.
16) Before that I have to do some cleanup as well. My Fedora LINUX box is nearly out of space. I have only few GBs left out of 120GB.
Point here is CEDRIC code works with MONTANA device.
This is the first time I am building a custom ROM and it was good to see most of the things working.
Updated you guys later tomorrow or a day after.
Thanks
KS
Hey. Thats really nice! I hope you share with us when its working
Maybe Ill try to build AOSP extended with your advice.
Hello,
@kalyansundhar , did you manage to advance on your rom?
will be some roms on moto g5s?When? I bought this phone today
I think we'll be more and more hope and wait for customs roms.
patgou.007 said:
I think we'll be more and more hope and wait for customs roms.
Click to expand...
Click to collapse
Main requirements are the device_tree and vendor_tree. Using system image dump, I tried my best to separate vendor and device files. But being a first timer, I couldn't do it. In other words, I am confused which file should go into vender_tree and which one to device_tree. But I haven't given up. Still trying to work out something. I am sure other experienced ROMers might also be working on coming up with a vendor and device tree. So let us wait.
Thanks
KS
Thanks for your hard work. We know it's not so easy. We have just to wait. And that, it's easy.
Device tree, Vendor blobs adn LOS7 build
Somehow I managed to come up with a device tree and vendor blobs for G5s.
Device: https://github.com/kayesk/android_device_motorola_montana
Vendor: https://github.com/kayesk/android_vendor_motorola_montana
Initial build of UNOFFICIAL LOS7 build is here: https://1drv.ms/f/s!Ahq68S0B7zYZjmVhmIHwvYGoz3gq.
This is completely based on STOCK. For any reason, if the shared file is not accessible, please let me know. I would upload it in GDrive.
The file size is around 450MB. Lot of clean up needs to be done. As I mentioned in my earlier posts, I don't have any mobile device software development experience. I played around the system image, placed files here and there, made some modifications and finally came up with this stuff. I don't know what files are used by the device and what are not. Don't laugh at me.
I request experienced developers help in fix issues. So feel free to access/modify source tree.
What works:
RIL (dual sim, volte)
WIFI
Tethering
Camera (Front and Back)
Bluetooth
Sensors
MTP
Sound
Fingerprint
Bugs:
Developer Options crashes. I think it could be permission related or some missing files may be. Whenever I hit the option, I get the following in logcat.
12-28 13:31:29.511 1805 3622 E UserRestrictionsUtils: Unknown restriction: null
12-28 13:31:29.515 1805 1862 E UserRestrictionsUtils: Unknown restriction: null
Not sure what it is.
Another issue is the inclusion of CMHW in Boardconfig.mk and CMActions in device.mk. When I include it in the build, I get the following error in logcat.
12-28 13:28:53.095 21735 21735 E AndroidRuntime: Process: com.cyanogenmod.settings.device, PID: 21735
12-28 13:28:53.095 21735 21735 E AndroidRuntime: java.lang.RuntimeException: Unable to create service com.cyanogenmod.settings.device.ServiceWrapper: java.lang.IllegalArgumentException: sensor cannot be null
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3226)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at android.app.ActivityThread.-wrap5(ActivityThread.java)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1586)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6186)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: sensor cannot be null
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at android.hardware.SystemSensorManager.requestTriggerSensorImpl(SystemSensorManager.java:205)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at android.hardware.SensorManager.requestTriggerSensor(SensorManager.java:1669)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at com.cyanogenmod.settings.device.SensorHelper.requestTriggerSensor(SensorHelper.java:108)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at com.cyanogenmod.settings.device.GlanceSensor.screenTurnedOff(GlanceSensor.java:56)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at com.cyanogenmod.settings.device.CMActionsService.screenTurnedOff(CMActionsService.java:95)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at com.cyanogenmod.settings.device.CMActionsService.updateState(CMActionsService.java:103)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at com.cyanogenmod.settings.device.CMActionsService.<init>(CMActionsService.java:72)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at com.cyanogenmod.settings.device.ServiceWrapper.onCreate(ServiceWrapper.java:47)
12-28 13:28:53.095 21735 21735 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3216)
Our device is not using a regular sensorhub stuff. It uses sensors.montana, sensors.rp and sensors.ssc. Above error could be related to that. Or may be a source code modification is required.
Everything works fine even without the inclusion of CMHW and CMActions, except the "Developer options" thing.
BTW, this build is for testing. So if you end up with a bricked/dead device by flashing this build, please don't hold me responsible. Flashing steps are as usual. Take a TWRP backup and Do a clean flash.
I haven't tried with GAPPS installation or rooting. But that shouldn't be an issue, I believe.
HAPPY NEW YEAR !!!
Thanks
KS
Many thanks for your work , maybe some developers will help us .....
{
"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"
}
[Unofficial] Pixel Experience for Mi5s
About Pixel Experience:
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
What works:
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Facelock
What isn't working?
Let me know
Gapps already included
Version Information:
Android OS: android-9.0.0_r35
Android security patch: 2019-04-05
ROM OS: 9.x Pie
ROM Kernel: 3.x Kernel-X by Hlcpereira
Minimum Firmware required: 8.11.8
Latest build: 2019-04-30
Status: Testing
ROM Sources: https://github.com/PixelExperience
Kernel Sources: https://github.com/Hlcpereira/kernel_xiaomi_msm8996
Download: https://mega.nz/#!yFshiYJT!-9H-_D5zkEiRX0epVsroR3Y3iDxfVjwLuseeppc59Pc
Disclaimer: I am completely new to Android ROM building, this is the first ROM I have complied so there is a good chance I cannot fix your bug. I will try to learn as I go.
For now I am just going to sync up with the Pixel Experience manifest and the common device tree so we have a build with the latest AOSP sources security patches and bugfixes.
Special Thanks to: Hlcpereira for developing and maintaining the official Mi5s Pixel Experience device tree, contributing to the common tree, providing his previous ROM builds and continuing his development on the Kernel-X project.
And jhenrique09 for without his continuous work in providing the official Pixel Experience this ROM would not have been possible.
XDA:DevDB Information
[Unofficial]PixelExperience, ROM for Xiaomi Mi5s
reserve #2
Previous Builds:
2019-03-06 https://mega.nz/#!SVl3gYDB!fkzi84-iwcDeXoXIvONQM6LR5p6ACttT5_RjT9Hq51Y
2019-02-07 https://mega.nz/#!bZNXkCQK!n2byOhKDkuK0bjjEE9ODU-yym5Mi5tD3YtU5j9DBLF4
what is this?
different thread from https://forum.xda-developers.com/mi-5s/development/rom-pixel-experience-t3871589 ?
nospec said:
what is this?
different thread from https://forum.xda-developers.com/mi-5s/development/rom-pixel-experience-t3871589 ?
Click to expand...
Click to collapse
Hi,
Yes I have continued on the build scripts of that ROM source as it has been discontinued from the previous maintainer.
thefulla said:
Hi,
Yes I have continued on the build scripts of that ROM source as it has been discontinued from the previous maintainer.
Click to expand...
Click to collapse
cool, thanks, hope for new update and support for this project
Edited since question was already answered.
All the best for the continuation of the project. All mi5s owners say thanks
Just flash this ROM. So smooth and stable.
Editing : Phone is Hanging and restarting again and again
adeelvirgo1984 said:
Just flash this ROM. So smooth and stable.
Editing : Phone is Hanging and restarting again and again
Click to expand...
Click to collapse
Are you using firmware 8.11.8 or higher?
Did you do a clean flash? (Wipe beforehand)
Have you applied any kernel changes?
I have been using since I built the ROM will see if other have same problem.
adeelvirgo1984 said:
Just flash this ROM. So smooth and stable.
Editing : Phone is Hanging and restarting again and again
Click to expand...
Click to collapse
In future when you complain regarding ROM, please provide Firmware version, Gapps version and any aditional modification that you used (root, custom kernel) and in what order you flashed them
Installed the ROM, latest build, with no keyboard at all, only voice input. And got stuck on start screen with 'Phone is starting' sign forever. Any one else got this?
RisingNoob said:
Installed the ROM, latest build, with no keyboard at all, only voice input. And got stuck on start screen with 'Phone is starting' sign forever. Any one else got this?
Click to expand...
Click to collapse
Are you using firmware 8.11.8 or higher?
Did you do a clean flash? (Wipe system, data, cache and dalvik beforehand)
Have you applied any kernel changes?
Dirty flashed this over the latest official. Stuck at the boot screen for more than 5 mins and it got hot, almost lost hope when finally it booted up. Rom is smooth so far. Nice work! Though perhaps it might need more checking as the Rom is lesser than 1Gb, PE builds are usually > 1Gb
kaitokid1412 said:
Dirty flashed this over the latest official. Stuck at the boot screen for more than 5 mins and it got hot, almost lost hope when finally it booted up. Rom is smooth so far. Nice work! Though perhaps it might need more checking as the Rom is lesser than 1Gb, PE builds are usually > 1Gb
Click to expand...
Click to collapse
I also made dirty flash, and it boot up but have problems with google play services. Its keep stoping. Already updated to newsest. Has any one have any advice how to fix it? I know about clean flash
thefulla said:
Are you using firmware 8.11.8 or higher?
Did you do a clean flash? (Wipe system, data, cache and dalvik beforehand)
Have you applied any kernel changes?
Click to expand...
Click to collapse
Solved it. I forgot this ROM already has GApps, had flashed them over the ROM. After figured this out I reflashed the ROM, now everything is fine.
BTW great ROM so far, let's see how it handles through the week.
Out of curiosity how do I check my Firmware?
macher91 said:
I also made dirty flash, and it boot up but have problems with google play services. Its keep stoping. Already updated to newsest. Has any one have any advice how to fix it? I know about clean flash
Click to expand...
Click to collapse
Usually dirty flash will do that...
It's look like its becouse of that:
02-12 09:43:13.263 15541 15557 E JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
02-12 09:43:13.263 15541 15557 E JavaBinder: java.lang.NoClassDefFoundError: Failed resolution of: Lorg/apache/http/message/BasicNameValuePair;
02-12 09:43:13.263 15541 15557 E JavaBinder: at uuk.a[email protected]@15.0.90 (100400-231259764):41)
02-12 09:43:13.263 15541 15557 E JavaBinder: at uuk.a[email protected]@15.0.90 (100400-231259764):2)
02-12 09:43:13.263 15541 15557 E JavaBinder: at uvr.a[email protected]@15.0.90 (100400-231259764):15)
02-12 09:43:13.263 15541 15557 E JavaBinder: at uvr.a[email protected]@15.0.90 (100400-231259764):11)
02-12 09:43:13.263 15541 15557 E JavaBinder: at ywa.a[email protected]@15.0.90 (100400-231259764):5)
02-12 09:43:13.263 15541 15557 E JavaBinder: at cqr.onTransact[email protected]@15.0.90 (100400-231259764):4)
02-12 09:43:13.263 15541 15557 E JavaBinder: at android.os.Binder.execTransact(Binder.java:731)
02-12 09:43:13.263 15541 15557 E JavaBinder: Caused by: java.lang.ClassNotFoundException: Didn't find class "org.apache.http.message.BasicNameValuePair" on path: DexPathList[[zip file "/data/app/com.google.android.gms-DZI54sU1ETluBRaEtWYhgA==/base.apk"],nativeLibraryDirectories=[/data/app/com.google.android.gms-DZI54sU1ETluBRaEtWYhgA==/lib/arm64, /data/app/com.google.android.gms-DZI54sU1ETluBRaEtWYhgA==/base.apk!/lib/arm64-v8a, /system/lib64, /vendor/lib64]]
02-12 09:43:13.263 15541 15557 E JavaBinder: at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:134)
02-12 09:43:13.263 15541 15557 E JavaBinder: at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
02-12 09:43:13.263 15541 15557 E JavaBinder: at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
02-12 09:43:13.263 15541 15557 E JavaBinder: ... 7 more
02-12 09:43:13.264 15541 15557 E AndroidRuntime: FATAL EXCEPTION: Binder:15541_3
02-12 09:43:13.264 15541 15557 E AndroidRuntime: Process: com.google.android.gms.unstable, PID: 15541
02-12 09:43:13.264 15541 15557 E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Lorg/apache/http/message/BasicNameValuePair;
02-12 09:43:13.264 15541 15557 E AndroidRuntime: at uuk.a[email protected]@15.0.90 (100400-231259764):41)
02-12 09:43:13.264 15541 15557 E AndroidRuntime: at uuk.acom.google.android.[email protected]@15.0.90 (100400-231259764):2)
02-12 09:43:13.264 15541 15557 E AndroidRuntime: at uvr.a[email protected]@15.0.90 (100400-231259764):15)
02-12 09:43:13.264 15541 15557 E AndroidRuntime: at uvr.a[email protected]@15.0.90 (100400-231259764):11)
02-12 09:43:13.264 15541 15557 E AndroidRuntime: at ywa.a[email protected]@15.0.90 (100400-231259764):5)
02-12 09:43:13.264 15541 15557 E AndroidRuntime: at cqr.onTransact[email protected]@15.0.90 (100400-231259764):4)
02-12 09:43:13.264 15541 15557 E AndroidRuntime: at android.os.Binder.execTransact(Binder.java:731)
02-12 09:43:13.264 15541 15557 E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "org.apache.http.message.BasicNameValuePair" on path: DexPathList[[zip file "/data/app/com.google.android.gms-DZI54sU1ETluBRaEtWYhgA==/base.apk"],nativeLibraryDirectories=[/data/app/com.google.android.gms-DZI54sU1ETluBRaEtWYhgA==/lib/arm64, /data/app/com.google.android.gms-DZI54sU1ETluBRaEtWYhgA==/base.apk!/lib/arm64-v8a, /system/lib64, /vendor/lib64]]
02-12 09:43:13.264 15541 15557 E AndroidRuntime: at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:134)
02-12 09:43:13.264 15541 15557 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
02-12 09:43:13.264 15541 15557 E AndroidRuntime: at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
02-12 09:43:13.264 15541 15557 E AndroidRuntime: ... 7 more
Click to expand...
Click to collapse
kaitokid1412 said:
Dirty flashed this over the latest official. Stuck at the boot screen for more than 5 mins and it got hot, almost lost hope when finally it booted up. Rom is smooth so far. Nice work! Though perhaps it might need more checking as the Rom is lesser than 1Gb, PE builds are usually > 1Gb
Click to expand...
Click to collapse
I'm not too sure why my builds are smaller, maybe the brotli compression was set to more aggressive compression. As far as I can tell my sources and build scripts are the same as previous developers.
Dirty flash can lead to weird issues in my experience..
RisingNoob said:
Solved it. I forgot this ROM already has GApps, had flashed them over the ROM. After figured this out I reflashed the ROM, now everything is fine.
BTW great ROM so far, let's see how it handles through the week.
Out of curiosity how do I check my Firmware?
Click to expand...
Click to collapse
Good to know
I know baseband (under settings -> about phone -> Android version) has something to do with firmware but I don't know how to decipher it to firmware version.
thefulla said:
Good to know
I know baseband (under settings -> about phone -> Android version) has something to do with firmware but I don't know how to decipher it to firmware version.
Click to expand...
Click to collapse
I got there, huge code under baseband with numbers and letters. Didn't even try to translate LOL
This is the first ROM that got with the complete Pixel recents menu. I'm afraid to lose this if I use Nova Launcher.
Have it any bugs
Or Freezing Problem
MI 5s cihazımdan Tapatalk kullanılarak gönderildi