Search results

>> screen auto-rotation does not work > Reinstall stock rom your persist is wiped Well that's what I did exactly. I mean right before Bliss I installed latest Chinese stock MIUI (not even MIUI.eu) in a naive hope to recover whatever I could have corrupted with previous ROMs and only then...

Hm... that's funny. If I use some external neodymium magnet (the one I use for pinning notes to a metal whiteboard) then the tablet wakes up. But the one which is built-in my cover doesn't wake the tablet on Bliss while does that on MIUI (as well as its derivative MIUI.eu). So I guess there must...

Just flashed, works quite well so thanks to all the BlissROM devs. One thing that doesn't work though is smart cover that used to work on MIUI ROMS before (like earlier today before flashing Bliss, i.e. all HW and magnet are in place). That's what I get from logcat when turning on "Enable Flip...

After update to the latest weekly (omni-9-20190630-clover-WEEKLY.zip) I can no longer enable Wi-Fi seeing the following in the log: 07-05 09:28:06.807 718 718 E [email protected]: Failed to write driver state control param: Invalid argument 07-05 09:28:06.807 718 718 E...

darkobas is there a chance to enable round corners in system UI? The point is real LCD in the tablet is plain simple rectangular one though screen cover "emulates" round corners. But if you look at any corner at a particular angle you may see those "hidden" corners of the screen which is well...

Interesting finding - even though I own Wi-Fi only tablet I'm seeing "Mobile network standby" consumes 22% of the battery when tablet is idling with screen turned off and nothing being run (like no music player etc). See attached screenshot.

Funny, that seems to be already solved exactly in the same way for all Omni ROMs, see https://gerrit.omnirom.org/#/c/android_vendor_omni/+/33461/

Probably I'm doing something wrong but once I flash Open GApps Nano for ARM64/"Android 9.0" the tablet is stuck in boot animation. Wiped data, system, vendor. I have 3Gb/32Gb non-LTE mi tab4. See logcat here: https://drive.google.com/open?id=1JOCvcJ2w5hRKsgn8GNGQZ-gWuUTA71y9 What looks...

I've just got "bluetooth.default.so" built from latest official sources (android-4.3_r1.1) for Galaxy Nexus with this patch applied https://github.com/CyanogenMod/android_external_bluetooth_bluedroid/commit/e6a380dbe5c269cf4b5ba95935e4e40cfb133032. Resulting file is attached to this post. Just...

From what I see on my phone there's a file "/data/data/com.android.email/files/deviceName" that contains device name. Exactly the one "androidc####". Why don't you try to change its contents manually and then try to connect to your Exchange server? Another question is why are you so sure...

So as of nightly from March 17 the fix is implemented and enabled Bluetooth no longer drains battery. https://jira.cyanogenmod.org/browse/CYAN-51 http://review.cyanogenmod.org/#/c/31201/

Indeed, Matrix kernel has this issue fixed with this commit: https://github.com/mathkid95/linux_samsung_jb/commit/0ca6ad998e09b7278475a3f363e29078253a454b Which is originally in CM kernel for aries (Galaxy S)...

As I promised, did some more study and filed an issue on CM issue tracker - http://code.google.com/p/cyanogenmod/issues/detail?id=7072 Seems like an issue is in kernel guts.

Still see the same issue on CM 10.1 M1 on Nexus S GSM. For me disabled bluetooth solves this issue (battery drain) but as soon as I enable bluetooth once again issue re-appears. Reboot, cache/dalvik-cache clean-up make no difference.

Could be, but the point is I had no Bluetooth enabled device nearby but nevertheless BT kept my phone awake (and BT icon in notification bar was gray saying that there's no active connection). I need to look into dmesg to find out what could be a real problem. I found something similar reported...

I'm on 10.1M1 and observed a really annoying battery drain: - CPU never got reached "idle" state, was always running at least at 100MHz - Settings-Battery was showing "Android OS" as a main battery consumer - Better Battery Stats showed "suspend_backoff" always triggered. After a couple of...

I'd say this is for security :) Both Exchange user or admin may trigger remote wipe procedure. But I don't think this is something that may happen without serious reason. I think there's another thing you should know about - on your N-th (most probably 3-rd) unsuccessful attempt to enter...

Please refer to these posts: http://forum.xda-developers.com/showpost.php?p=30270006&postcount=451 http://forum.xda-developers.com/showpost.php?p=30311260&postcount=462 The first one says that in v3.2 (targeted to Jelly Bean devices and above) we now leave device admin (enforced by Exchange...

Sales started in Russia today. Most computer store networks have it in stock now.

Please check: 1. if "adb.exe" is in your PATH 2. If you have Google's USB driver installed - http://developer.android.com/sdk/win-usb.html

Well, that note makes me completely happy. Thanks a bunch for your work!

rustamabd, do you think if we may leave ability to wipe device remotely? I believe since we now have local admin active we may leave this sometimes vital functionality. Note that if one has MS Exchange 2010 installed on their server users may wipe their devices from OWA (Outlook Web Access).

So here's a screen-shot of a stack trace on Exchange service crash. and from it I'd say that patched version faces problems :) These lines are important markers I believe: ====================== java.lang.SecurityException: No active admin...

Well, I was to lazy to try to dig a bit deeper. But inspired by previous message I attempted to do patching manually. And I discovered that the only noticeable difference is in *.apk names. And here're names for Google's Jelly Bean: EmailGoogle.apk - Email Exchange2Google.apk - Exchange To be...

Hi there! Here's another voice for Jelly Bean support. But I'd like to ask if you have any ideas why this patch is not working correctly on JB? I may volunteer for trying things on JB device if you don't have a target to play with.

Well, for some reasons ADB is not working properly in VirtualBox - https://www.virtualbox.org/ticket/6620 Spent few hours - and no luck. So I decided to get some luck in Ubuntu. And after some attempts succeed here. And here's how: 1. Install wine (is needed to run "7z.exe" later) 2. Install...

rustamabd, do you think if we may find sources of this pretty helpful utility? Actually what I want is to run this patch utility in Linux (Ubuntu) environment. But as I learnt from failed attempt to run it in linux there're hard-coded paths to some external executables etc. In general prebuilt...

I guess you should see corresponding messages at least in logcat. Unfortunately I didn't have a chance for in-depth look at logcat output for this particular case (modem restart) but may imagine that from message content you'll find out that is is about modem. If you find corresponding lines...

The first thing I'd suggest is to check if you have the most recent "radio"-firmware flashed in you device. Because your symptoms are pointing to telephone module problems which might be solved in more recent firmware than you have at the moment.

Unfortunately the day I said ther's no pin-protection in MIUI they fixed it and starting from MIUI 1.7.29 one have to enter PIN on screen unlock if Exchange policy asks you to (((

BTW guys, why don't you check MIUI Rom for your device? At the moment there's no PIN-locked screen unlocker. I'm not sure if it is a bug or it is by design but even if your Exchange policy forces you to enable PIN-protection of screen unlock nothing really changes. I mean you never get PIN...

Are you sure that call recording is supposed to work on Nexus S? AFAIK call recording should be somehow supported in Linux kernel. Stock kernel for Nexus S doesn't have those patches applied to enable call recording. I suppose kernel from MIUI is quite close to the stock one. On the other hand...

In my case stock MIUI kernel resolved the issue)

Installed 1.3.7 cfs on MIUI 1.7.8 and noticed 2 issues: 1) Camera app didn't respond on screen taps and keys, while I saw a motion picture in the "viewfinder" window. 2) SpuSpy statistics: 50% of time - 1000 MHz 50% of time - deep sleep And as a consequence the back of my Nexus S was extremely...

Hi DEADover, just googled this thread while trying to solve just the same problem on my Nexus S. Just the same bahavior on 1.7.8 (in my case it is Russain one, but as you see, seems like it is not the reason). Camera worked fine on -> 1.6.24 and then I flashed 1.7.8 today and got the problem...

Got the same (no camera support in Skype 2.0 on 1.6.24). I thought that device identification comes from /system/build.prop which in case of MIUI differs from stock one. So I tried to reproduce strings related to model name and then rebooted. But nothing happened. My current strings are...

Yep, here I'm with you. I did come back to stock 2.3.3 just to find out if those instability issues were due to you know hw defects whatever. And I was surprised how flawless was my experience with stock one. But then I tried Netarchy kernel and got more that a week uptime w/o probs. And was...

Well, but don't you notice a bunch of minor fixes that make CM7 experience differ from stock Android? What about "Silence mode", Messaging app with black background, "Incognito mode" in web-browser, these days even access to corresponding settings with long tap on power widget (whether it is in...

This approach really works. I mean erasing existing recovery before flashing new one (at least 3.0.2.4) helps new recovery start ok.

Hi ogdobber, just looked into my phone info and was quite surprised: 120 hours uptime with no issues at all. I guess the reason is Netarchy kernel I flashed last week. And since flashing no reboots. It is 1.3.0.2-CFS version (2.6.35-11-netarchy-nexus-1.3.0.2-cfs-natas). So I think your...

Here you are) http://www.mediafire.com/file/hbw6yvwn1beapnl/FroyoMailUnlocker.zip

Unfortunately I tried your kernel 1.4.7 while being on CM7 RC4 and got bootloop once. That might have been caused by some crap left from RC2 and RC3 I tried before. BTW if your kernel only differs from CM stock with Voodoo and BLN do you think these two additions might fix stock kernel issues...

Got CM7 release with "stock" kernel (I mean kernel from CM7) flashed after OEM Lock-Unlock, formatting data/system/cache partitions from CWM. After about 30 hours uptime got black screen with buttons lit. Device was just lying on the table, no charging, no 2g/3g toggling, nothing. The same I saw...

Patched email app on stock Android 2.3.3 Gingerbread BTW, I just got working patched email.apk on Nexus S with rooted stock Android 2.3.3 I had my patched email.apk from CM7 rom I created last week while running CM7 on my device. So steps to replace stock Gingerbread Mail app are here: 1. Get...

Bronk93, Please make a number of pictures of your mount and could you please name a model of your mount also. Regards, Alexey

What a nice one! But where did you bought it? Seems like it is still not available in Samsung web store.

Try Dialer One https://market.android.com/details?id=kz.mek.DialerOne&feature=search_result

I believe the most problems with smartphones are in software, not hardware. And software could/should be patched/updated.

Got mine for 2 weeks. No screen protectors, pouches etc. No scratches at the moment.

Got mine 1.5 weeks ago, waited for 2 days, there were no OTA, manually updated to 2.3.3, a day later to CM7.