This was a google choice. Btw you don't understand that the problem is windows not the phone.The only tedious thing with KK for the sd card management is the disappearance of /android/obb...
Maybe not.This was a google choice. Btw you don't understand that the problem is windows not the phone.
Sent from my nexus 7
I was talking about mtp drivers not obbMaybe not.
I've activated the tdb with Cwm recovery with all the wipes possible (to have the miui on sys2)...after flashing the last cyano in sys1 and connecting to the PC via USB, /android/obb was there, visible to winzozz ...
then it disappeared, I think restoring apps with titanium backup or enabling Android debugging (though if I disable debug, /obb still remains invisible to windows)
On sys2 with miui the same, /obb invisible to windows.
I use adb and Android commander for now. If someone knows a solution, let me know
http://forum.xda-developers.com/showthread.php?t=2522538Oh,where to download theme packs???
Yes of course are the drivers but the situation wrote above is quite strangeI was talking about mtp drivers not obb
Sent from my nexus 7
Bugs. Gem Flat (alarm clock bug...). Flats - Notification panel switches of different sizes. Mianogen - maybe.Best themes (imo) :
Gem flat
Flats
7KP264896A278024E.We talked a lot about lags in the last few weeks. As you may already know I've fixed this and everything works fine now - well except for me
It seems that during kernel development - especially during the experiments to fix the lcd driver I somehow damaged my lcd.
The final proof was that via MHL everything is perfectly smooth.
don't worry, a lagging lcd won't keep me from developing but this totally sucks during daily usage -_-
thx @linuxx for testing
Were them a soft or hard reboot? (If it show grey mi logo it was hard)I like cyanonen, but I received several spontaneous restart on cm-11-20140425 and on cm-11-20140510. My MI2S is on the table and suddenly restarts. Is there any log where I found out what was going on. I think it will be some applications.
I did wipe data/factory reset, wipe dalvik cache before install 20140510 and I used Slim_minimal_gapps.4.4.2.build.4.6.zip
0VB58319SP044451GSounds like you need a beer
Gesendet von meinem MI 2 mit Tapatalk
Thanks. I'm not sure with grey mi logo, I remember only CM logo. I will try it with file.Were them a soft or hard reboot? (If it show grey mi logo it was hard)
If hard upload on paste.ubuntu.com /proc/last-kmsg (immediately after the reboot)
Inviato dal mio MI 2 utilizzando Tapatalk
Today again, it was hard with mi logo.Thanks. I'm not sure with grey mi logo, I remember only CM logo. I will try it with file.
You had a kernel panic, that's why it rebooted. Keep WiFi disabled when you don't use it (profiles may be useful, set "when disconnect from WiFi [name] > set profile" and make a new one with WiFi disabled until m1cha fixes thisi am getting hard reboots too, seems like a wifi problems. 10/05 build.
http://paste.ubuntu.com/7456542/
Today again, it was hard with mi logo.
Don't seem like fatal error from pepa henzl.
http://paste.ubuntu.com/7457336/
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation