yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] nikagl:
Sorry, no CUS. See below.

That's ok, I have seen someone else upgrade from RC17 too, and that was ok. Not sure about speaker though, haven't seen that issue yet... you have Single or DUO-sim?

Updater in the download rom above does the following checks:

(!less_than_int(1411648279, getprop("ro.build.date.utc"))) || abort("Can't install this package (2014年 09月 25日 星期四 20:31:19 CST) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "acer_e3" || abort("This package is for \"acer_e3\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "e3_emea_gen1");

So install will only continue if:

ro.build.date.utc < 1411648279

ro.product.device = acer_e3

ro.product.name = e3_emea_gen1

Check your build.prop for the above values.

Regards,

Nika.
[Miscellaneous Android Development] hackwerk:
Really strange!

I have never done updates besides via automatic Acer OTA system.

So if I check my build.prop I get ro.build.date.utc=1401428187 and the other two are the same as you say!

My system does NOT update and says I am up to date (with this 1.016 JB 4.2.2)...
[Miscellaneous Android Development] nikagl:
I wish I knew why. I am not sure how updates are pushed. Do you have an alu folder and if you do, there's nothing in that folder? I have checked using WIFI, didn't have a SIM or SDCard in the device as I daily use my S510. Had to insert the sdcard to download the file, but it already notified when I turned the device on and it connected to WIFI...

---------- Post added at 05:17 PM ---------- Previous post was at 05:04 PM ----------

I now see you have vaches CWM recovery! I would first flash stock recovery and boot, just to be sure...
[Miscellaneous Android Development] Adge40:
I've tried for the update on a totally stock untouched e3 and device is up to date on jellybean in the uk
[Miscellaneous Android Development] :
Well , encryption still not working with this one ... and it will still reset your phone if you even try ... I guess no encryption cookie for E380

Also:

- Authenticator still working

- Flashed with CWM over previous KK leak without Wipe without issues except loss of root (quickly resolved since CWM is not lost)
[Miscellaneous Android Development] nikagl:
Strange. Still don't understand why it was pushed to my device.

Hmmm... must have previously misunderstood what authenticator is. Never tried using two-way-authentication in google so not sure how it's supposed to be working. In my case I've turned it on in the google website. Mail, etc., stopped working (logical). Then installed the authenticator app, but when I scan the QR-code (after activating the app on my pc) and enter the code the authenticator app it keeps mentioning it's the wrong code. Is that the behaviour you are seeing?

Regards,

Nika.
[Miscellaneous Android Development] eksuka:
My ALE3 is rooted. Now that I receive notification to upgrade to KitKat, is it safe to just do it over the air?

If it is, is it easy to root KitKat version? An un-rooted phone is a no-no to me.
[Miscellaneous Android Development] hackwerk:
Thats terrible, AND strange, because Google wants to force encryption now (in Android L) right?!

Please chat/ask Acer about this MAJOR issue!?
[Miscellaneous Android Development] nikagl:
Let's first thoroughly test this before jumping into conclusions. My encryption works fine. Not too much experience with encryption either, but is encryption executed through Recovery? If so, CWM may cause this issue, and if you want to encrypt your device, it might be smart to first flash stock recovery. Beware, I haven't had time yet to see whether flashing a new recovery works... I am traveling abroad the next days and may not have too much time this week either.... To encrypt my device I did the following:

1. Have full stock device on 1.016 (JB), updated to 1.018 (KK)

2. Set 6-digit pincode

3. Encrypt device from security

4. It rebooted, I saw the Acer logo with white backround and then the LEGO Android (encryption logo). Encryption took about 8 minutes...

5. Type my code to decrypt storage

6. It rebooted again (acer logo with white background again)

Please also describe your authenticator issue, see my steps and my issue:

1. In my case I've turned it on in the google website. Mail, etc., stopped working (logical)

2. Then installed the authenticator app

3. When I scan the QR-code (after activating the app on my pc) and enter the code the authenticator app it keeps mentioning it's the wrong code.

Is that the behaviour you are seeing?

Regards,

Nika.
[Miscellaneous Android Development] :
About the encryption issue. Well that's completely true ... I always tested encryption with CWM and with a rooted device. And I'm the only one who reported this issue so far (with this leak and the previous). Root is not negotiable for me but I could be ok with a stock recovery I guess.

Will try with stock recovery and report back :)
[Miscellaneous Android Development] nikagl:
I tried authenticator on other device and the above steps worked fine, so guess that's a kk issue with Acer devices (tested it with e380 and s1)...
[Miscellaneous Android Development] :
Well I tried with stock recovery and it still failed "for me" ... so I don't know ...

I also have xposed framework installed and my device is also rooted.

RIght now we only have two tests:

User A (myself):

- Latest KK (not updated with OTA) / CWM / Rooted : encryption fails (with or without factory reset)

- Latest KK (not updated with OTA) / Stock Recovery / Rooted : encryption fails (with or without factory reset)

User B (nikagl)

- Latest KK (OTA) / Stock Recovery / Unrooted : encryption succeeds

What would be really useful is for someone else to try encryption with KK , CWM / Root ... It would only takes a few minutes to test ... Just do a nandroid backup first , try , if it fails just restore backup from CWM and you're good ... This would rule out if it's an issue with just "my device" or an issue with "modded devices".

It seems from other posts I saw that adb logcat will work during encryption process so I'll try that to see if I can log an error on my side.
[Miscellaneous Android Development] :
So I logged the encryption failure with adb logcat

and here it is :

D/Cryptfs ( 122): Just use muxreport to stop modem
D/Cryptfs ( 122): Just asked init to shut down class main
D/Cryptfs ( 122): unmounting /storage/sdcard0 succeeded
D/Cryptfs ( 122): unmounting /data succeeded
D/Cryptfs ( 122): unmounting /protect_s succeeded
D/Cryptfs ( 122): unmounting /protect_f succeeded
D/Cryptfs ( 122): Successful: mount tmpfs for '/data'
D/Cryptfs ( 122): Just triggered post_fs_data
D/Cryptfs ( 122): post_fs_data done
D/Cryptfs ( 122): Just use muxreport to start modem
D/Cryptfs ( 122): Just triggered restart_min_framework
E/Cryptfs ( 122): Crypt_ftr version doesn't support persistent data
I/Cryptfs ( 122): Enabling support for allow_discards in dmcrypt.
[B]E/Cryptfs ( 122): Cannot load dm-crypt mapping table.[/B]
E/Cryptfs ( 122): Encrypting filesystem in place...
[B]E/Cryptfs ( 122): Error writing crypto_blkdev /dev/block/dm-0 for inplace encrypt[/B]

After that , it fails and that's about it ... It's the only error I see

And I have absolutely not the slightest idea of what's wrong :p
[Miscellaneous Android Development] Timmmmaaahh!:
I'm wondering this as well, running several paid-for apps that require root. Not getting any update notification though (Belgium). Currently on "Acer_AV052_E380_1.005.00_EMEA_BGCs", System updates say "Your device is up to date." (just checked).

Plus, I got a 32GB SD card (2 partitions: FAT32 22GB + Ext2 10GB) which is used by Link2SD. Could that cause any trouble? Some Google apps are linked.
[Miscellaneous Android Development] Adge40:
I updated to rc18 kk with 16gb sdcard with fat32 partition, whenever linking with link2sd it asked to reboot and then after reboot totally deleted the app including system apps
[Miscellaneous Android Development] hackwerk:
Official update to KK (20141007)

There it is!! Huray huray huray!

The official KitKat (4.4.2) update (625MB) is being pushed to my device since a couple of hours. My device (E380 DUO, see sig) is in The Netherlands, and was on official OTA 1.016 JB.

I Will make a backup and try it, although I am scared about my Link2SD etc, especially after last post above this...

Update 0

: This SUCKS. ALL my apps (in Link2SD) are gone! Even though I did a CWM recovery install plus SuperSU and Root Restore on first boot (right after apps optimization)! Any solution for this without reverting (I have a CWM backup)?!

Update 1

: You need stock recovery installed, or it will error (red triangle) and reboot.

Update 2

: The update will restore recovery, boot logo, boot animation to stock and unroot! Normal root method is still working, so perform it after first boot.

Update 3

: You can easily fix/restore all your Link2SD apps, by restoring root (normal CWM flash / SuperSU method) and after second reboot starting Link2SD (as root) and selecting Ext4 as SD type. After third boot Link2SD will search SD and restore all links/apps! Perfect! I am updated and NOTHING seems lost or really changed!

Update 4

: Play store icons (black icon background when transparant) are fixed. New background is set. All of my (root) apps are working/running! Even TextSecure as sms app, and Droid Protector, etc! Dont have to (re)login or reinstall or reconfigure any of my apps yet besides my banking app! Great!

Update 5

: Very happy with this update! GPS is WAY BETTER (super accurate and very fast!)and CAMERA is FIXED (perfect and fast focus)! Some widgets are unpinned and some theme settings are changed, but thats no biggie. Also SD Card 1 (ext) is now SD Card 0 and 0 (int) is now 1 (only in Android, in CWM it's as usual (0=int/1=ext)).

Update 6

: Strange, but I can not reinstall my custom boot animation (via zip). Is this protected now!? Also backup in CWM (recovery) takes way longer (data partition)?!

Update 7

: Just as fast or faster than JB, and same battery use for now. Also it fades out and in when turning on or off. Best thing yet is that the High Headset Volume Warning is REMOVED! Hurray!

Ps1.

Please try the one click simple root apps/tools after update, and give me a shout if one of the tools WORKS on our new KitKat (Kingo? VRoot?? Etc???)!
[Miscellaneous Android Development] Schumi_wk:
No update atm in Belgium for a single simcard device.
[Miscellaneous Android Development] Adge40:
My dual sim rom e3 has update but my single sim doesn't have the update??
[Miscellaneous Android Development] Timmmmaaahh!:
Thanks Adge40 for the heads up and hackwerk for the update news. It does look like only dual sims are getting the KK update (or any official updates for that matter)... What gives, Acer? Single SIM users not good enough for ya? :eek:
[Miscellaneous Android Development] Timmmmaaahh!:
Can I simply flash the latest 635475739172038202_OTA_Acer_1.0_AV052_A.zip to my E380 (single SIM)? If so, what tool should I use?

Current status:

Baseband: MOLY.WR8W1248.MD.WG.MP.V5.P51, 2014/04/24 13:38

Kernel: 3.4.5 st2@st2-srv#1 Fri May 30 14:11:56 CST 2014

Build: Acer_AV052_E380_1.005.00_EMEA_BGCs

Custom build: 1401430347
[Miscellaneous Android Development] Shreps:
If you "know what you're doing" you can :

- Flash CWM 6.0.5.0

- Make a full Nandroid Backup with the reco (and duplicate it on your PC)

- Make a full backup with SPFT if you can

- Flash the DUAL Sim ROM from CWM

and let's see how is it going :)

In case of problem, the Nandroid backup should be enough to restore your current system
[Miscellaneous Android Development] :
hackwerk ... would you mind tryng the encryption on your rooted / cwm / device ? (after a nandroid backup)

from my latest tests ... it seems it doesn't even wipe your phone anymore ... It just fails the encryption but if you power off at that moment it will boot fine nothing changed.
[Miscellaneous Android Development] hackwerk:
Bugs KK

Any KK bugs or problems yet?

1) Encryption is under investigation now by me and nn0madd etc. (Interesting post about it in general by VICE btw)

2) Robberg is having the problem of GPS working fine, but in all different apps always having a 0 km/h movement (when moving)...

3) ???
[Miscellaneous Android Development] Adge40:
I still had sd card access problems,I tried all partitions I.e. ext 2,3,4, fat 32,I tried all sd card fix apps and all link/app2sd apps,none worked,I had to flash back to 4.2.2,I'm wondering whether it's because I flashed vache's dual SIM Rom to my single SIM phone???,p.s. single SIM owners on fb are saying they've not had the update
[Miscellaneous Android Development] tiliarou:
Updated yesterday to KK and it seems to work quite well !

I tried using OTA voodoo rootkeeper but it failed to restore the root after update so I used the CWM recovery method and it worked great.

One annoying thing is that I cannot quickly switch the sim card I want to use while in the SMS app. I used to dropdown the notification bar and there were 3 buttons to choose (sim 1, sim 2, always ask).

Now I have to dropdown notif bar, expand settings, click on the Message icon and change the behaviour for sending SMS... Very annoying !!!

Also, I noticed that I got 2 force close of System.UI when editing the quicklaunch buttons of the notif bar. Then I had to reboot the phone to get the buttons to work properly...

I noted today that the battery drain seems faster than with JB but that might be just an impression or because of a reset calibration maybe ?
[Miscellaneous Android Development] hackwerk:
No crashes/FCs here, battery life seems normal and the speed is amazing!

I love this new KitKat a lot and it has made my (our) phone way better if you ask me!

No problems or bugs whatsoever (yet)!

Btw, the ROM should work on all E380 versions, so just give it a go! If you have problems with any part of it (like SMS) just use a different (better!) app (like TextSecure, the future of SMS, also built-in in CyanogenMod!).

Done:

XDA Added a Q&A subthread to our thread (see top just below title), where you can ask (stupid) questions if you like, without messaging me (great!) :D

I added a poll (see top of the thread).

I changed Voodoo OTA Rootkeeper to Not Working (anymore in KitKat).

I won't try encryption myself as I see too many disadvantages, like no possibility for frameworks etc

New version of SuperSU (2.13) is released, inc compatibility with Android L. BusyBox was also updated. A lot of other versions in the TS/FP are updated.

Questions:

Please test the new versions of VRoot and Kingo (see TS/FP) on KitKat to get root?

Anyone tested encryption a little more elaborate?

Anyone with the GPS speed bug (not me)?

Anyone found a place where I can get the LCD unit to replace my cracked one, for a decent price?!

I noticed Wipe Battery Usage Stats is gone from CWM, is that normal (obsolete?)?!
[Miscellaneous Android Development] Fmlover:
Has anyone managed to get Viper4android (Sound mod) works after kitkat update?

can't live without this app :(
[Miscellaneous Android Development] hackwerk:
Well I've seen this tutorial movie on it, but this is what I always think about these kind of apps:

1) 100 settings for 1 thing (sound) make it very complicated;

2) Why use a huge thing looking like a sound studio on a very cheap crap sound chip and even cheaper 2-bit speaker!?

3) Why wouldn't the phone brands test and try out and set sound to the 'best' quality/volume already (although we also have DTS app, and CyanogenMod users the famous DSPManager)?!

NOT my intention to start a flame/discussion over this, but a few intelligent reactions can't hurt (and may get me convinced!?).
[Miscellaneous Android Development] tiliarou:
I can confirm the problem I have... My battery went from 55% to 15% in only one night, with nothing turned on except the normal GSM/3G signals of 2 sims (no data).

Moreover, I also have problems in general, for exemple when sometimes when I turn on 3G data for 1 sim, the connection is not made and I don't receive nor can send any data. When I go into the settings, I cannont turn on airplane mode nor turn off a sim card...

Also, whenever I reboot my phone, the default keyboard is reset to stock Google one and Swiftkey becomes disabled.

Very strange as no one is having those problems it seems. I tried disabling most of my Xposed modules, and uninstall Unbounce.

One thing that comes to my mind : when I flashed the SuperSU update zip in CWM (6.0.5.0 from Vache), and when I choose to reboot, it asked me if I wanted to fix permission (don't remember the exact message) and I said yes. Could this be related to the default keyboard not registering ? And all my troubles related to permission issues ?
[Miscellaneous Android Development] nikagl:
I haven't seen this type of issues before on Acer devices, and I doubt fix permissions could have caused this. In the past this was a required part of every custom ROM, and if you didn't do it it could cause this type of issue or even bootloops. It sounds like your upgrade was done only partially and some components may not have correctly been upgraded.

You can try several things:

1. Make sure to make a backup - did you make it before the upgrade too?

2. Try wheter factory reset fixes your issues - just to confirm it's not the system/rom but some app causing this. Restore from the backup if it behaves the same

3. Possibly try to run the upgrade again? I think this might be impossible because the upgrade checks the ROM date/time. You may need to go back to an older ROM to do this and in that case it would be similar to factory defaults

Let us know what you choose to do.

Regards,

Nika.
[Miscellaneous Android Development] hackwerk:
I have never been happier so I really think your update is F'ed up. Dit you do the official OTA? Always, so the previous installation was also OTA? Did a factory reset already (I didn't with pure official OTA's only)?

My machine is running like never before?! Better battery life and faster, en all old problems solved and nothing new! :cool:

(And yes it always asjs to Fix my root too in CWM (which I do to be sure) but whatever)
[Miscellaneous Android Development] tiliarou:
Ok, thanks for your inputs hackwerk and nikagl.

My phone has only been through official OTA update, and rooting once with Kingo, then with CWM. Didn't try factory reset nor reflash yet but I guess I have to !

So the next step is just boot in CWM recovery, do a factory reset (wipe data ?) and that's it ? Should I wipe all and flash the latest official OTA to be sure ?
[Miscellaneous Android Development] nikagl:
Hold on, one more thing to try. Did you try "clear cache" from CWM? That also fixed this type of issue on other devices. Just do it, and you'll see the "updating apps (1/200)" screen after rebooting (will take a while). This will rebuild the cache for all current apps for the current machine.

If not, I would make a backup with CWM (just to be sure, for your personal data) and factory reset through the Backup & reset Settings (Settings - Backup & reset - Factory data reset) of the device (ie. not from CWM). I am not sure whether you can flash the OTA as it contains the check for the date/time. You can try, before factory reset, to see whether it fixes the issue as we suspect some faulty upgrade/install of the device.
[Miscellaneous Android Development] Brick3d:
Custom rom on the way!

Hi all,

I have ported Color OS today!! most of it is working (phone calls, wifi, 3g data etc) but it has a few issues...

It doesnt mount the internal sd card like it did on stock rom, any clues for this? i replaced vold.fstab already but nothing, changed the storage list in framework.res apk too

camera isnt working (either FC or green screen if i open it) modified the ramdisk now with some values for testing it out...will let you know

please help on the sd card issue!!!

Brick3d
[Miscellaneous Android Development] Shreps:
Hi,

You will have to check the ramdisk of your boot

Did you made some modifications ? using the stock E3 boot ?

I think you have to make a mix of ColorOS Ramdisk and Stock E3 Ramdisk
[Miscellaneous Android Development] kissman21:
hi guys ;) here is official OTA update for "emea_cus_1" ;) copied from SDcard before update run ;)

Android version: 4.4.2

Build: Acer_AV0K0_E380_1.002.00_EMEA_CUS1

http://uloz.to/xiQk2SnZ/update-zip
[Miscellaneous Android Development] Brick3d:
I have looked in the ramdisk for mount points but couldn't find anything..any leads on what files i need to look into? The internal card not mounting results in serious issus like the play store not updating etc..
[Miscellaneous Android Development] tiliarou:
I cleared cache through CWM and it seems that problems are gone... I will continue to investigate. Anyway, thanks for your help guys, I hope it's not too much off topic !
[Miscellaneous Android Development] Shreps:
Thanks, but can you upload it on another site (Gdrive ?) ? I can't download from this one.
[Miscellaneous Android Development] Shreps:
Try to look for fstab files (in both ramdisk and in /system) and try to see if you can add/modify an entry about internal storage
[Miscellaneous Android Development] hackwerk:
Great! Youre the pioneer of us I guess.

I see that porting ColorOS with camera is already a bottleneck on XDA.

I see a lot of negative comments everywhere, including the strong advise to use CM (11S) above ColorOS (would be my brand of choice!!). Besides that OnePlus already dropped ColorOS and will develop a new own ROM for the Chinese market.

-Paranoid mode ON-

This (OnePlus One) OPPO ColorOS (2.0) is Chinese. It can only be found on the Chinese phone models, while international models get CM11S?!

Is it totally open source and safe and secure?! Where can I found best info besides; Here on ColorOS.com, or at their FB, or the OPPO ColorOS Forum, or XDA or ???

-Paranoid mode OFF-

Ps1. Great, 350 posts! Congrats to all :)

Ps2. Don't forget to vote in the poll (on top)! Seems almost everyone is quite/very happy with our phone. (Didnt expect that)
[Miscellaneous Android Development] Brick3d:
[MENTION=4493088]Shreps[/MENTION], thanks for the fstab intel!! checked boot.img and there is some different files, rebuilding the rom now for testing :)

And Hackwerk...

CM would be my rom of choise, but we all know how the development on that goes. I need a rom which is stable for daily use, custumizable and good-looking (at least its what I aim for). Because of that, Lewa, MIUI and ColorOS are roms of my choice...

as for the camera...it is functional (although i had my doubts with panorama mode but ill have to check the libs, I think the issue lies there), but its "only" 8MP...

I'll keep you posted :good:
[Miscellaneous Android Development] hackwerk:
Thanks Brick3d, it was no offence!

CM we all know will stay a dream maybe.

You tried MIUI yet? ColorOS seems to be dropped, and MIUI has a future I guess?? Again, where can I find more concrete info on those?

Also I must confess that now that I have a PERFECTLY smooth and fast running stock KitKat, my need for custom is a little less :)

But go on! I am very curious of course!!
[Miscellaneous Android Development] Brick3d:
No offense taken at all!! but given the diversity of the needs of fellow cookers and rommers, I wanted to make my PoV clear :)

Havent given miui a shot...always seems a bit laggy to me (ported it to multiple devices already) compared to lewa os < that one is still in my list of favourites :)
[Miscellaneous Android Development] nicollivier:
Hi There,

Since I'm using the KK version, I cannot find the way the customize the ring for the second SIM.

Any tips?!

Thx

Nicolas
[Miscellaneous Android Development] nikagl:
Hmmm... you don't have the SIM1 and SIM2 Ringtone setting?
[Miscellaneous Android Development] nicollivier:
It's really strange....

When my phone is in French, I don't have the option (French screenshot)

But I've got it in English version

Thanks for your help :)
[Miscellaneous Android Development] nikagl:
Well...looks like the translation is wrong...in English there's no way to configure the sound for video calls? Did you try to change that and see whether it actually changes the ringtone of the second SIM?

Same in Dutch btw! :)