I have the Y cable and a USB battery pack. I'd like to get OTG to work with any 5.0 or 5.1 based ROM (even stock would be fine). I've tried installing CM 12.1 and a couple different kernels and haven't had any luck so far. I know that my flash drive is getting power because the light blinks. Can someone walk me through exactly how to do this?
Some of the questions I'm having:
* I'm not exactly clear on which kernels have OTG, which do not, and if an additional patch is required. I've done some searching and a lot of the information is old (for Android 4.X.X).
* Once I install a kernel thats supposed to have OTG support, do I need to enable it somewhere? In some cases I've tried installing Synapse, but I haven't found an option for it.
* Do I need to install any additional apps to use it? If not, how will I know that its working? Will any notifications show up when I plug in a USB device? Will my flash drive show up in the Cyanogenmod file manager?
So I finally got OTG to work with an older kernel (hells-Core-b47-kk from this thread). Problem is now the colors blue and red are swapped on screen. This is probably because its an old kernel for Android 4 and I'm on CM 12.1. Anyways, at least I was able to answer some of my own questions.
You do need to install additional apps. CM's built in file manager is useless. When you plug in a device, there will only be a notification if an associated app is installed. ES File Explorer works with flash drives.
I've tried Hell's Doctor, Matr1x, AK, and Franco's and haven't had any luck with any of them. Can someone point me at a 5.0 or 5.1 kernel that they know works, or tell me what I might be doing wrong?
Have you tried stick mount by chainfire?
Sent from my Nexus 5 using XDA Free mobile app
Stickmount works for mounting flash drives but I mainly wanted OTG for other devices, so that doesn't really help.
unlimitedbacon said:
So I finally got OTG to work with an older kernel (hells-Core-b47-kk from this thread). Problem is now the colors blue and red are swapped on screen. This is probably because its an old kernel for Android 4 and I'm on CM 12.1. Anyways, at least I was able to answer some of my own questions.
You do need to install additional apps. CM's built in file manager is useless. When you plug in a device, there will only be a notification if an associated app is installed. ES File Explorer works with flash drives.
I've tried Hell's Doctor, Matr1x, AK, and Franco's and haven't had any luck with any of them. Can someone point me at a 5.0 or 5.1 kernel that they know works, or tell me what I might be doing wrong?
Click to expand...
Click to collapse
Colors swapped becase you most probably flashed AOSP version on CM, try flashing the latest stable b69 CM VARIANT
I see. Thanks. I kinda did the opposite and flashed stock 5.1 and the patched b47 kernel. I couldn't find anything that said mainline hell's core does OTG. Does it?
Ok I finally figured this out. Heres everything I did:
Flash Factory 5.1 Image
Flash CWM Recovery
Root
Install Quanta v2 AOSP Kernel
Install Quanta Tweaks
Enable OTG in Quanta Tweaks
Install USB Host Diagnostics by Chainfire
Run diagnostics. It will detect an issue and magically fix it.
Celebrate
Can this procedure be used to make a sandisk otg pen drive work on a nexus 4?
unlimitedbacon said:
Ok I finally figured this out. Heres everything I did:
Flash Factory 5.1 Image
Flash CWM Recovery
Root
Install Quanta v2 AOSP Kernel
Install Quanta Tweaks
Enable OTG in Quanta Tweaks
Install USB Host Diagnostics by Chainfire
Run diagnostics. It will detect an issue and magically fix it.
Celebrate
Click to expand...
Click to collapse
Thanks for the detailed information! A couple of days ago I flashed Quanta V6 kernel on Euphoria but I got plenty of app crashes and ended up wiping and reflashing all the phone. I will give another try next weekend, with a proper nand backup first.
Is there some way to do what QuantaTweaks does to enable OTG via an adb shell?
I have a Nexus 4 with a broken touch screen but I would like to work with it until I can get a new touchscreen.
---------- Post added at 05:03 AM ---------- Previous post was at 04:50 AM ----------
unlimitedbacon said:
Ok I finally figured this out. Heres everything I did:
Flash Factory 5.1 Image
Flash CWM Recovery
Root
Install Quanta v2 AOSP Kernel
Install Quanta Tweaks
Enable OTG in Quanta Tweaks
Install USB Host Diagnostics by Chainfire
Run diagnostics. It will detect an issue and magically fix it.
Celebrate
Click to expand...
Click to collapse
This worked great! Have you found anything that works with marshmallow. I am open to flashing new ROM or kernel. Spent a lot of time on this alas. I have tried Chroma ROM with taurus, quanta v10, hells-core but had not luck.
After you do the above procedure do you still need a USB Power Y Cable or you can connect directly a USB stick to N4?
Nexus 4 with Android 5.1 OTG
Hi
I thought I would add my solution for Nexus 4 with Android 5.1
After rooting I used the Matr1x kernel (http://forum.xda-developers.com/nexus-4/orig-development/kernel-matr1x-v13-5-kk-4-4-t2007231
& http://matr1xkernels.com/matr1x-news/matr1x-kernel-for-android-5-0-lollipop )
This kernel has the OTG already added as well as lots of other tweaks - so far it seems OK with 5.1.1
I also had to do the trick with USB Diagnostic tool and let it try to "fix" the problem - it seems to add a missing file in the permissions directory
( https://github.com/452/USBHIDTerminal/wiki/How-to-enable-USB-host-API-support)
As far as I read the main reason that OTG was removed from the Nexus 4 was because it wasnt able to power the devices correctly.
So I would definately recommend using a powered OTG Hub.
Hope that helps someone
Thanks
Adrian
Related
now i flashed my a 500 with the light speed rom 1.04 and everything is fine and the 3g usb is working also fine
why do i need to
update the Kernel to thor's kernel version 3.5
what is the value added from this update
You don't NEED to update it, but doing so gives you lots of extra features such as additional USB device drivers and overclocking support.
For specifics of his kernel, you'll need to go to Thor's website
FloatingFatMan said:
You don't NEED to update it, but doing so gives you lots of extra features such as additional USB device drivers and overclocking support.
For specifics of his kernel, you'll need to go to Thor's website
Click to expand...
Click to collapse
So to update it i will download from there
http://www.tegraowners.com/?p=1016
then put it in the sd card
then boot and choose install zip file from memory card and nothing will affect the room i had
Just wipe cache and dalvik before you flash it.
Sent from my Acer A500 using xda premium
What is the latest modded kernel for 3.1? Could I use a 3.2 kernel with 3.1 mod?
Doubt it but had to check...
Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
cubeth said:
Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
Click to expand...
Click to collapse
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
taodan said:
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
Click to expand...
Click to collapse
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
cubeth said:
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
Click to expand...
Click to collapse
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
taodan said:
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
Click to expand...
Click to collapse
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
cubeth said:
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
Click to expand...
Click to collapse
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
korockinout13 said:
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for your advice, I'll try to follow it and see if it works as soon as I've got back home.
Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!
krkeco said:
Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!
Click to expand...
Click to collapse
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc
Thanks for the quick reply, is that the 27 or the 33 / 84 download?
sites.google.com/site/bpearuploads/
Or does it not matter?
opssemnik said:
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc
Click to expand...
Click to collapse
Got it figured out thanks to your help!
Hello, guys and girls.
So, I'm not an expert like most of you. I need help.
I will explain you what happend with my Nexus 4: I installed CyanogenMod 11 with the installer some weeks ago. Yesterday, I installed an app called "Touch Control", which would allow my phone to have Knock On feature. But it installed a kernel that would make this work. That kernel have MANY bugs, such as Wi-Fi do not work and changed colors. My phone does not have internet, because I don't have mobile data.
I do not have TWRP or CWM, just the simple CyanogenMod Recovery. And I can't install anything because of internet (I can copy .apk to my phone and insall it).
Here is what I would by happy to do: change that kernel to the default one (I didn't make its backup) or to any other kernel that works.
Ask, please, for any detail that can help.
Thank for you to reading my post.
Just something else: I don't want Knock On feature anymore. I just wan't my phone working properly.
What you did was install a AOSP kernel on a CM rom, that does not work well as you might have noticed, you need to dirty flash CM11 to get the default kernel back.
nibla101 said:
What you did was install a AOSP kernel on a CM rom, that does not work well as you might have noticed, you need to dirty flash CM11 to get the default kernel back.
Click to expand...
Click to collapse
I have a question: when I flash CM11, will the kernel be replaced? I heard that the kernel in Android phones is separate from the operating system.
caiodanielnunessantos said:
I have a question: when I flash CM11, will the kernel be replaced? I heard that the kernel in Android phones is separate from the operating system.
Click to expand...
Click to collapse
Yes it will, all roms come paired with a kernel otherwise they would not boot.
When you dirty flash CM11 it will replace ur /system and /boot(this is where the kernel is) but it will leave ur /data and /sdcard so your apps and settings remain.
nibla101 said:
Yes it will, all roms come paired with a kernel otherwise they would not boot.
When you dirty flash CM11 it will replace ur /system and /boot(this is where the kernel is) but it will leave ur /data and /sdcard so your apps and settings remain.
Click to expand...
Click to collapse
Thanks, I will try this.
The most easy way to get back to stock kernel (no matter which android u currently have) is to use a toolkit like Wugfresh and select the stock kernel option.
Only think u need is a pc with internet and the phone to be connected with the cable.
Xperia Z3 Compact, CyanogenMod 12 - official nightly
Since 2015-01-21 CM12 nightly available.
Working:
- calls
- sms
- 2G, 3G, LTE DATA
- sound (2 speakers are ok)
- bluetooth
- camera + video recording are ok
- wi-fi
- GPS
- Compass
- NFC
- OTA update
Reported bugs:
- Audio calls work over loudspeaker, it's usable, but uncomfortable.
- Calling app somebody is a bit laggy - Try turning off "Phone number lookup" in dialer settings
- built in Audio Fx seems to be buggy on BT
- USB OTG
Solved bugs:
- auto brightness is buggy - SOLVED 2015-01-27
- the recovery is _EXTREMELY_ hard to read. It looks like a black screen but if you look closer the brightness is set to minimum or something. - SOLVED 2015-01-27
Download Links:
CyanogenMod 12:
Nightly: link
Changelog:
http://www.cmxlog.com/12/z3c/
Instalation:
- backup current ROM
- download and put cm12 ROM on external SD
- extract kernel from this cm12 zip (boot.img) and flash in fastboot / fastboot flash boot boot.img
- power up phone, go to recovery mode
- do a full wipe
- select Aplly Update -> chose from sdcard1 -> select cm12 nightly zip
- after finish reboot phone
Google Apps i got from here: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900 I pick "micro version of gapps"
Click to expand...
Click to collapse
Thanks to veimus for instalation help
crimpy1 said:
Since 2015-01-21 CM12 nightly available.
Download Links:
CyanogenMod 12:
Nightly: link
Click to expand...
Click to collapse
Great, is there a rls log? Or gerrit which shows wants not working?
Sent from my D5803 using XDA Free mobile app
shafiq01 said:
Great, is there a rls log? Or gerrit which shows wants not working?
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
Changelog:
http://www.cmxlog.com/12/z3c/
Should this thread be posted ?
Does cyanogenmod installer work with z3c
Is it possible to flash it through twrp?
I have kitkat rom now with 23.0.1.A.5.77
Does it require lollipop as base OS before I can flash this *.zip
Sent from my D5803 using XDA Free mobile app
No, you have to flash kernel first from CM12 zip to have a recovery that can handle Android 5
My Easy way is:
- backup current ROM
- download and put cm12 ROM on external SD
- extract kernel from this cm12 zip (boot.img) and flash in fastboot
- power up phone, go to recovery mode
- do a full wipe
- select Aplly Update -> chose from sdcard1 -> select cm12 nightly zip
- after finish reboot phone
Google Apps i got from here: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900 I pick "micro version of gapps"
shafiq01 said:
Is it possible to flash it through twrp?
I have kitkat rom now with 23.0.1.A.5.77
Does it require lollipop as base OS before I can flash this *.zip
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
You have TWRP? Where'd you get that?
I have androplus kernel v19c on top of rEctiFy ROM which has the DRM fix baked into the ROM. Awesomeness.
But androplus kernel supports multiROM. Whether it can take the app https://play.google.com/store/apps/details?id=com.tassadar.multirommgr i don't know. But if it could then it would perhaps be possible to have both my current ROM (Kitkat) and the CM12 ROM. In that manner I would have a daily driver and CM12 to boot between. But first I will try the instructions given with the kernel from CM12, I guess it's inside this nightly build?
Sent from my D5803 using XDA Free mobile app
@op, a bunch more info would be cool, what does work, what does not, known bugs and so on...
tapatalked from lollipopped i9300
flashing fails in cyanogen recovery, and i can't use the adb shell to un dim the recovery screen.
im pretty sure i had adb enabled in dev mode before i started.
is there a fix for that?
I saw this on xperiablog, already downloaded the latest build but didn't try and install it yet. It would be great if someone who tried it posted here what works and what doesn't.
I had it for day, and what works:
- calls
- sms
- 2G, 3G, LTE DATA
- sound (2 speakers are ok)
- bluetooth
- camera + video recording are ok
- wi-fi
- and almost all was fine for me..
And now problems:
- auto brightness is buggy
- high battery consumption when my phone was paired to bluetooth car speaker
- from power menu option Reboot = power off
- LED notification are working but you can`t force to different colours (i.e. if i want setup blue color for SMS its always ~amber), charging/battery LED are OK red/orange/green
Anyone able to confirm that the magnetic charger works?
veimus said:
I had it for day, and what works:
- calls
- sms
- 2G, 3G, LTE DATA
- sound (2 speakers are ok)
- bluetooth
- camera + video recording are ok
- wi-fi
- and almost all was fine for me..
And now problems:
- auto brightness is buggy
- high battery consumption when my phone was paired to bluetooth car speaker
- from power menu option Reboot = power off
- LED notification are working but you can`t force to different colours (i.e. if i want setup blue color for SMS its always ~amber), charging/battery LED are OK red/orange/green
Click to expand...
Click to collapse
wow, sounds nice, i would indeed like to have it as well
but i'm failing on flasing part through cyanogen recovery twice now
first i did the way as mentioned in the thread, then i tried the jerpelea thread method by adding the aries in the script
no success, maybe it could be that my external sd card is formated as exFat32, so i could get larger files than 4GB.
meaning cyanogen recovery can't read, perhaps?
now i i've restored my kitkat nandroid backup twice through twrp(nut) after fastbooting androplus kernel.
I've installed it as well now, so far everything seems to work. Auto brightness is indeed buggy.
To get it installed I had to do a few things:
- Extract boot.img from the cm12 zip and flash it with fastboot
- boot into recovery (power up) , the recovery is _EXTREMELY_ hard to read. It looks like a black screen but if you look closer the brightness is set to minimum or something. Turn off all lights (LOL) and flash cm12 followed by gapps.
- unlock developer options to enable root
shafiq01 said:
I have androplus kernel v19c on top of rEctiFy ROM which has the DRM fix baked into the ROM. Awesomeness.
But androplus kernel supports multiROM. Whether it can take the app https://play.google.com/store/apps/details?id=com.tassadar.multirommgr i don't know. But if it could then it would perhaps be possible to have both my current ROM (Kitkat) and the CM12 ROM. In that manner I would have a daily driver and CM12 to boot between. But first I will try the instructions given with the kernel from CM12, I guess it's inside this nightly build?
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
MultiROM support requires some work to make the z3c a compatible device - androplus kernel (v19c) has the required kexec-hardboot support for multirom, but multirom manager doesn't support the z3c and no multirom custom TWRP... I would have a go at porting Multirom, but I don't know coding with C very well.... If anybody can code in C, there is a porting guide by the dev here: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
---------- Post added at 10:39 AM ---------- Previous post was at 10:28 AM ----------
shafiq01 said:
wow, sounds nice, i would indeed like to have it as well
but i'm failing on flasing part through cyanogen recovery twice now
first i did the way as mentioned in the thread, then i tried the jerpelea thread method by adding the aries in the script
no success, maybe it could be that my external sd card is formated as exFat32, so i could get larger files than 4GB.
meaning cyanogen recovery can't read, perhaps?
now i i've restored my kitkat nandroid backup twice through twrp(nut) after fastbooting androplus kernel.
Click to expand...
Click to collapse
I had the same problem, tried three times (even shut myself in a really dark room to see if i could read the recovery logs!) - I started thinking the issues must be with accessing my external sd card (mount issues?), so I moved the cm rom zip to internal/sdcard0 and flashed again, it worked perfectly! Done the same thing with Gaaps, worked!
We really need TWRP (or CWM) as the cm recovery is a bit pants (no offence intended to CM), no nandroid backup/restore, mount tools etc).
I have spent about six hours playing with and "customising" the rom - I'll post my experiences/issues soon...
Translate
Thanks
A lot of big update on next nightly , I
I would like to know how translate CM12 ?
I find this for CM11 : https://crowdin.com/project/cyanogenmod
but nothing for CM12 and no files strings.xml here : https://github.com/CyanogenMod/android_device_sony_z3c
Thanks
mick711 said:
Thanks
A lot of big update on next nightly , I
I would like to know how translate CM12 ?
I find this for CM11 : https://crowdin.com/project/cyanogenmod
but nothing for CM12 and no files strings.xml here : https://github.com/CyanogenMod/android_device_sony_z3c
Thanks
Click to expand...
Click to collapse
Looking forward to all those changes. I'm tempted to try this as a daily driver for a few days, but the brightness is driving me a bit nuts having to set it manually. Don't see any fixes listed for it in the next nightly.
I installed and seens all fine. Couldn´t install using TWRP from AndroPlus Kernel. Needed to flash the CM boot.img and than try to read the recovery menu lo/
But all seens fine, so far
For next, nights, all i need is wipe cache/dal and apply update like now?