Related
[ROM][32A RADIO 6.35]Eclair w/ Nexus1's 3D gallery CAM & most things are working well
this ROM is for Sapphire 32A SPL 1.76.2007 and latest Radio 6.35.07.29.
pure AOSP build, google bits and gallery are added. (make sure you think you have the rights for using the apps from google, i just make some copy for you)
thx: Cursordroid, Enomother, Cyanogen, RA, jnwhiteh, ChainsDD, sober (who have full of courage for testing my first kernel ) , and more...
what's new: less crash, more stable. new gallery app which use hardware accel. a new step to full working with our new radio.
the update.zip, just push it into ur sdcard then apply it from recovery: http://www.4shared.com/file/202007372/5352e8b4/my2x.html
mirrors:
http://hotfile.com/dl/24995574/2b6c9d7/sanpei_eclair32a.zip.html , by asero, thanks
http://www.megaupload.com/?d=5TH7FNC0 , by akai21, thanks
http://hoegsberg.net/fileshare/Sanpei Eclair 2.1/ , by Eukanaba, thanks
if you are a 32A user with old radio, and you want a upgrade or try this ROM, follow Cursordroid's instruction to Update your 32A Magic to 6.35.07.29 Radio and 1.76.2007 SPL
working (update: all confirmed by me or other users):
camera
gps
wifi
mobile data
sensor
lights
gps
bluetooth
openGL
Gallery3D
googlebits
working but leaving some questions open:
playback (will print error message in log, not tested with many format)
not working properly:
camcorder (only preview working)
I would not say "it is very fast", but I feel it fast enough. and if you do not care about the multi-media things, i think this build seems not bad.
(for the multi-media things, they are mostly caused by media libs in AOSP, which google have not done yet. (but i cannot understand why nexus-one can have a stable version !!!) it is not all the HTC/Qualcomm's fault, Google didn't do their job very well too)
if there are something I missed, or I made some mistake, don't be sulkiness plz. i will fix them with you. let us make it better and make more 32A user switching to new Radio, with more users, we can do better and more quickly.
file/things includes:
AOSP master, I keep it at the API version 5, because things with API 7 for other devices (except nexus1) are not stable, i don't want to pretend that we have a nexus1, and make things unstable.
su and superusers from ChainsDD.
kernel which i modified from msm-kernel-2.6.29.
libhtc_ril.so, omx libs are from a leaked official 2.x ROM. camera libs, libgps.so from another one. (thanks the man who provided them)
libhtc_acoustic.so and some miscs files from official 1.5 ROM. akmd too, but akmd from 1.6 ROM have newer version and i think it will works too.
google bits are come from different sources too:
Gallery3D/google framework parts from nexusone dump, i think Enomther deodexed them, thank you and I LOVE YOU.
Other google's things are versions used everywhere, and here are my thanks to the one dumped them --> m(_ _)m.
cyanogen's patch which is directed towards infinite sync. it may be a temporary workaround, when google do things right, i will remove it.
.......
more: lock screen and wallpaper is the eclair's initial one as AOSP source released with them. if you want other lock screen, customize it yourself, and tell me how ^^, I'm really not a good cooker .
known issues and workaround:
1. camcorder can not record, but it didn't crash anything as previous one (with my kernel, from jnwhiteh) would crash some.
2. video playback has many errors the video can be played though. just reported by logcat, and no more thing will happen in my tests.
3. if you stay in the Gallery3D UI, and the phone sleeps later, when it wake up, the Gallery3D lost hardware acceleration. you can quit and enter this app again, it will be fine.
4. first boot with google bits may not go without a hitch. you can remove all google apps in the zip (you must resign it) and push them later.if you boot with googlebits:
you will see a dialog let you choose the default behavior, select SetupWizard here. if you select another, you can not use internet during the first boot, it will say "no connection", though we are connected.
the SetupWizard will start twice, the second one is for asking you to sign in a google account, you can just press menu to quit.
and there are many lags in first boot, maybe black screen (can not light, you can "adb reboot" it) or some crash (i have met once for each and I flash it serveral times) if you operate too fast.
after second boot, it will works fine. it seems if we give the phone more time to do many initialize jobs, it will work happily even in first run.
5. with superuser, if you select deny, the app which needed the permissions may be force closed. it is a bug in su sources i used which is not belong to me and i have no time to look and fix it yet.
update:
6. when wake up the phone, screen turned on, but backlight of screen not. if you can see image, just go to setting and set brightness, then the light will open. need more reports (like situation/logcat/dmesg, etc.) to locate the problem. i encountered this problem once.
7. "died in sleep", this problem has been encountered by others, personally, i met it once during first run, after a reboot I never met it again. but I don't think this problem just appears during first run. instead, i think the situation of first run is more closed to the condition triggering it.
I think there must be more problems, let us find them together, and fix them by our hands.
update: after some search I found that some softwares (like nettraffic) will cause more "died in sleep" in some ROM/kernel/Radio combination. and many kinds of "died in sleep" can be avoid with some tweaks, but i don't know if they are same problems as ours, and i can not get what this tweaks are (or why, how..) from anywhere yet.
i am waiting for more details to fix 6 & 7. I will be grateful if someone can provide some info about similar problems, since I had seen these problems in some other ROM/kernel/Radio combination.
and guys who encountered these problems, could you provide more details plz? something like: occurred during first run/other, with situation XX (mobile/wifi/software X running, etc) which you think it caused the problem occurred more often. if you can reproduce it, we will get very closed to fixing them.
great job!
Another ROM using the latest SPL/Radio... great!
Downloading now.. will try flashing later...
Nice work sanpei!
Great job. I will try it immediatly.
Excellent, nice to see some other developers working on this radio/SPL version as well!
I will definitely be trying this out today!
Awesome will try when I get home from work.
Would it be possible to implement the Nexus apps-menu in a later build?
bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!
asero said:
bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!
Click to expand...
Click to collapse
I will look into this, but I cannot locate this problem quickly, since I just met it once during a first boot, and it never appears again.
is it like the situation "die in sleep" in some build which are based on CyanogenMod? (when i was using old radio)
can you reproduce the problem and description the operations? thx.
Eskibo said:
Awesome will try when I get home from work.
Would it be possible to implement the Nexus apps-menu in a later build?
Click to expand...
Click to collapse
maybe or maybe not is there anybody who have the right skills could try it for us? (i have some other things to do) i will join later.
Newb questions
Hi Guys,
Sorry for the lame newb questions. I just want to verify this prior to trying this ROM.
I'm currently using CursorSense 1.0.1 - which is my every day ROM (great functionality, fast, does everything I need)
I'm really interested in trying out Android 2.1 - and seeing as this uses the same SPL / Radio - it means I should be able to just wipe and flash this one. HOwever seeing as I just want to take a peek and play around with it, I don't want to screw up everything on my phone toooo badly lol.
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten
asero said:
bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!
Click to expand...
Click to collapse
I encountered this issue too. I also encountered this issue once with aosp-2.0.1-jnwhiteh-r6.
Gritten said:
Hi Guys,
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten
Click to expand...
Click to collapse
Yes.. backup, wipe, flash, try, wipe, restore.. I even think that last wipe isn't even necessary, but it doesn't harm either. A Nandroid restore restores your phone exactly as you left it (incl. your call log, SMS, apps, etc.)
It could be that some new folders/files are created on your SD card (if required by Eclair apps), but since they are not used by your previous rom it won't be a problem (unless you don't want to keep those unused folders and files on your SD card).
If you are not sure, or don't want to keep the extra folders/files, you can always make a backup of your SD card on a USB or PC prior to trying the rom.
Have fun! ;-)
Gritten said:
Hi Guys,
Sorry for the lame newb questions. I just want to verify this prior to trying this ROM.
I'm currently using CursorSense 1.0.1 - which is my every day ROM (great functionality, fast, does everything I need)
I'm really interested in trying out Android 2.1 - and seeing as this uses the same SPL / Radio - it means I should be able to just wipe and flash this one. HOwever seeing as I just want to take a peek and play around with it, I don't want to screw up everything on my phone toooo badly lol.
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten
Click to expand...
Click to collapse
Yes. You can restore from nandroid backup and everything will go back. I often switch between CursorSense 0.4 and sanpei's rom several times a day.
so can anyone answer if this is a good everyday rom? or equivelant to cursor sense?
shael said:
so can anyone answer if this is a good everyday rom? or equivelant to cursor sense?
Click to expand...
Click to collapse
The ROM is well done. It's responsive (no lag from my playing) even the 3d gallery ran very well.
I didn't use it too long for everyday items as I'm a Sense fan, however I find that standard plain Android is pretty empty when I don't have my sense stuff on top lol.
Definately play around with it if you're interested.
sober said:
I encountered this issue too. I also encountered this issue once with aosp-2.0.1-jnwhiteh-r6.
Click to expand...
Click to collapse
Me too!
Awesome ROM.
Keep UP dude!
Been testing it for a few hours. So far not a single FC and i can confirm that BT works just fine, also OBEX with Bluetooth File Transfer by medieval software.
SMS and emails send and get received just fine.
Tested the GPS in both google maps and the GPS status app to check efficiency, and so far everything works just fine.
The gallery is really sexy, now we just need to get the Nexus1 apps-menu implemented .
Actually there are three other things i'd like implemented also:
Animated desktop
Wireless tether
Google Nav
What do people think about that?
Eskibo said:
Been testing it for a few hours. So far not a single FC and i can confirm that BT works just fine, also OBEX with Bluetooth File Transfer by medieval software.
SMS and emails send and get received just fine.
The gallery is really sexy, now we just need to get the Nexus1 apps-menu implemented .
Actually there are three other things i'd like implemented also:
Animated desktop
Wireless tether
Google Nav
What do people think about that?
Click to expand...
Click to collapse
Will be even better with u suggestion and Sense!
fabioccoelho said:
Will be even better with u suggestion and Sense!
Click to expand...
Click to collapse
I wish I had some idea of how to do those things, then I would surely try help doing it.
Hi P999 users. Ive been experimenting with the Eagles Blood ICS ROMs and wanted to post some of my findings. I am not allowed to post in the relevant developer area where a detailed report would be useful so I will just post my feelings about the ROM's here for the next few weeks, until I am allowed to post more useful information.
I started out on the CM9 version of Eagles Blood, and then switched to a nightly AOSP ROM two weeks ago. I wanted to find out with AOSP was all about. This build felt very smooth. However crashes and force closing have cropped up in the past few days and this made me feel uncomfortable with the ROM's stability.
An update was released on the 20th so I felt the need to backup with Titanium and install the new ROM.
While installing the new ROM I read a notice in the changelog which confirmed my suspicion about the frequent new force closing. It seams there was some file corruption happening in previous builds... Maybe this was the reason mine was having issues??? How do I feel about this?
Anyways, after installing the newer ROM, and restoring my backup things were out of whack. Something about the restore had left some systems settings unusable and my Data connection was not working. Everything was force closing, even the android keyboard. I re-wiped and re-installed the ROM and backups with the same issues.
I decided to go back to build 4.0.3 and things have been good since. I had a feeling my Titanium backup was ruining my AOSP installations so this time I took a selective approach to restoring apps and did not restore system settings. My data connection is working again and my apps are working well. (Just to be clear I went back to the CM9 based version of EGB and not the AOSP version I was using which became unstable over time)
I do appreciate the AOSP development on behalf of EGB team but will be staying with the CM9 build for stability sake until file corruption issues are dealt with.
And that's how I feel about that.
the file corruption issue is your issue though, how are they supposed to fix your backup from your phone? Don't restore the settings and system, just apps. I don't get what the big issue is...
good job
mt3g said:
the file corruption issue is your issue though, how are they supposed to fix your backup from your phone? Don't restore the settings and system, just apps. I don't get what the big issue is...
Click to expand...
Click to collapse
MT3G thanks writing verbatim the solution I wrote into the OP.
*edit* the file corruption issue and the titanium backup fiasco are not related. It is my understanding that EGB team is aware of corruption cause by the early ASOP release and that they are working on it. I've decided not to use the AOSP version until they take care of it. (Solution / Workaround #1)
Maybe this is a big issue for someone who would not make the connection between restoring a system backup and the data connection not working anymore. I felt this was good information and that's why I posted it (Solution / Workaround #2)
Yeah that's why I never back up or restore any type of system settings; always gets you trouble.
Glad to see you're a problem solver , we don't have much of those here.
exactly my thoughts, most people wold just freak out and say the rom was stupid or something, I read the post as he was saying he is going to wait for EB team to fix the issue where as it isn't going to be "fixed" lol. Unless you are updating the same rom or a rom that hasn't been extremely updated then it's possible for it work out okay. But using cm7 backing up and then going to cm9(4.0.x) and restoring is going to be a no go probably. i'm with Buru though except I just stay away from TB all together, I only use about 12 apps and no games.
update
Just a quick update. Its been almost 3 weeks on the EGB CM9 build 4.0.3. I've been very happy with it. Occasionally I install updates and I get strange behavior after. I've found that rebuilding permissions after an update is a good practice.
buru898 said:
Yeah that's why I never back up or restore any type of system settings; always gets you trouble.
Glad to see you're a problem solver , we don't have much of those here.
Click to expand...
Click to collapse
I have restored email (with all accounts, data and app) as well as saved wifi locations before. I believe both of those are system settings and they never caused problems.
Sent from my LG-P999 using XDA
Try using GoBackup for apps, contacts (if you don't sync to your gmail), and some system settings. I like it more than TB. I'm not saying it won't cause FC's and that's because I don't know. But it might work better.
Hey, I've done a fair whack of searching and unfortunately even though I've done a lot of lurking and reading, I do not have permission to post in the developers forum. Supposedly I need 10 posts before I'm able to post inane drivel to spam up the threads.
Annnnnyway, I've had a crack with a few of the more popular SMS apps, along side the native Messaging app, and all of them crash immediately on launch. The exception is Go SMS Pro, which is unable to detect any SMSes or even send any SMSes.
I've no clue how or why this is, I've cleared both my normal and Dalvik cache, the MMS.APK is in place in /system/app/ folder, the permissions are correct, I've tried clearing the data, and I think short of a full wipe and install, unless someone can point me in the right direction, I've tried most things a reasonable person would think of. Granted, I'm not knee deep in Android development like a few of the people who lurk around here, so I could be mistaken.
I'm running a standard HTC Sensation with a slightly out of date version of the default 1.5GHz kernel included with Android Revolution HD, although I am planning on flashing the latest TamCore to see if that will clear it up (though I doubt it). Currently I have OpenSensation-20120809-NIGHTLY.zip installed, but I'm downloading OpenSensation-20120810-NIGHTLY.zip as well in hopes that maybe it's a bug in this nightly that is resolved in the newer one, although I doubt that.
Anyway, any help is much appreciated.
Cheers.
toejam316 said:
Hey, I've done a fair whack of searching and unfortunately even though I've done a lot of lurking and reading, I do not have permission to post in the developers forum. Supposedly I need 10 posts before I'm able to post inane drivel to spam up the threads.
Annnnnyway, I've had a crack with a few of the more popular SMS apps, along side the native Messaging app, and all of them crash immediately on launch. The exception is Go SMS Pro, which is unable to detect any SMSes or even send any SMSes.
I've no clue how or why this is, I've cleared both my normal and Dalvik cache, the MMS.APK is in place in /system/app/ folder, the permissions are correct, I've tried clearing the data, and I think short of a full wipe and install, unless someone can point me in the right direction, I've tried most things a reasonable person would think of. Granted, I'm not knee deep in Android development like a few of the people who lurk around here, so I could be mistaken.
I'm running a standard HTC Sensation with a slightly out of date version of the default 1.5GHz kernel included with Android Revolution HD, although I am planning on flashing the latest TamCore to see if that will clear it up (though I doubt it). Currently I have OpenSensation-20120809-NIGHTLY.zip installed, but I'm downloading OpenSensation-20120810-NIGHTLY.zip as well in hopes that maybe it's a bug in this nightly that is resolved in the newer one, although I doubt that.
Anyway, any help is much appreciated.
Cheers.
Click to expand...
Click to collapse
Might be an issue with OpenSensation (as you're using nightlies). Back up what you have, format everything but SD card, and I'd recommend trying a completely different non-nightly ROM, try AOKP m6. This way you can see if the SMS issue is related to OpenSensation or not. backup m6 THEN try the newest OpenSensation nightly to see if the issue is fixed. This way you'll likely be left with at least one ROM you can restore with working SMS functionality.
I might yet have to do that, although I would prefer to stay as close to vanilla as possible, that's why OpenSensation interested me - I think I'll try regressing to the CM9 RC2 on the official Cyanogen mod website first, then try other projects after that if that doesn't work. Does seem strange that no one else is complaining of this issues though, and I really can't see myself being the only one running the latest versions.
Oh yeah, the newest nightly and Tamcore kernel didn't work - the only thing that's changed is now I know I can't regress directly to my ARHD backup, yay!
This one's a bit of a thinker.
Well, I did a full wipe, installed the latest HyperSensation CM9 build and reinstalled the TamCore Kernel. Everything seems to be working now.
Thanks for the input, thread can be closed.
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Reserved
Build 5 was pretty stable, interested to see what has changed.
Tapatalked from Desire S running Andromadus
Build 5 was first build i used of AOSP 4.2 and it was fantatic experience, i never expected 4.2 to work so flawlessly on desire s so fast after release. And to be honest i did not see many bugs.
So i flashed build 6 and i was not disapointed, as you said you will release only stable and advanced releases and it was the point with 4.2 build6.
It would be nice to see official changelog, but i have noticed some nice little resize job done and few small glitches fixed.
I just found one thing i dont know how to fix. On android keyboard swype Lithuanian dictionary doesnt work. It is not in official list until i refresh it and then it pops up and i install it ( it worked well with build 5) and with build 6 it just doesnt work, and when i return to dictionary list there is no Lithuanian dictionary again .
Sensors are not working properly. When i make a call, screen turns off even when i don't block the sensors and it stays that way till the time call is going
Sorry man posted it in wrong thread. Its for andromadus cm 10.1 but do look into the matter as its really is irritating
Sent from my Desire S using Tapatalk 2
Thanks for the info..
Why there is no Google Now on lock screen? Only unlock option...
I have latest gapps, updated Google Search etc.
Taranis said:
Why there is no Google Now on lock screen? Only unlock option...
I have latest gapps, updated Google Search etc.
Click to expand...
Click to collapse
That's just the way it is for 4.2, Google made it that way.
I thought I saw videos on YT with Google option on 4.2...
Taranis said:
I thought I saw videos on YT with Google option on 4.2...
Click to expand...
Click to collapse
Yeah, that is for devices with On Screen buttons (Galaxy Nexus or Nexus 4/7/10). For those, the buttons are replaced with a dotted circle on the lockscreen, swiping up from which opens Google Now. Since AOSP doesn't officially support any device without hardware buttons, Google probably thought that it would be best to remove the option from the lockscreen, since swiping from the buttons opens that anyways
Trouble with bluetooth
Hi,
Thanks for your work on this rom!
I would like to report an issue with the Bluetooth functionality in this (and earlier) versions of this rom. In my circumstance it doesn't produce an error of crash.
For example. My phone is connected with a handsfree carkit (parrot) and when entering the car it recognizes the phone, asks for pin code and 'gets connected'. The problem is that the phone is not visible (as usual) on the handsfree device and the overall functionality does not work.
If I can be of any assistance in this I'll gladly be of help.
Thanks for your work!
Well Google switched the bluetooth plugin in 4.2 from bluez to bluedroid. It has been causing issues across devices, even Nexus 7 has issues. As Flinny said we can't do much unless someone upstream fixes it.
Read more here...
http://forum.xda-developers.com/showthread.php?p=35093862
Tapatalked from Desire S running Andromadus
Anyone know why the sound disappear?. notifications, alarms, ringtones, ect.
Thanks for the enlightenment!
suku_patel_22 said:
Well Google switched the bluetooth plugin in 4.2 from bluez to bluedroid. It has been causing issues across devices, even Nexus 7 has issues. As Flinny said we can't do much unless someone upstream fixes it.
Read more here...
http://forum.xda-developers.com/showthread.php?p=35093862
Tapatalked from Desire S running Andromadus
Click to expand...
Click to collapse
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
- dictionaries other than English doesn't work with swype keyboard feature,
- some people wrote about bluetooth audio issues.
ROM is very smooth, hope it will be smooth in next builds. Great work!
Taranis said:
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
- dictionaries other than English doesn't work with swype keyboard feature,
- some people wrote about bluetooth audio issues.
ROM is very smooth, hope it will be smooth in next builds. Great work!
Click to expand...
Click to collapse
camera animations do lag sometimes and some pictures you take tend to not show up in gallery after you have taken them.
As for battery all i can say is :highfive: battery is almost same in all 4.0/4.1/ 4.2 roms AND it is not at all bad here. I managed to get from full charge(100%) to 81% in 30 hours. I doubt many roms can do something like this in low-med usage.
Other then that this rom is my personal favorite until someone release 4.2 rom with better theme or perfomance.
The only thing i lack in here is conservative cpu governor and maybe little undervoltage.
Taranis said:
Flinny, almost everything works great.
Issues I found (AOSP build 6):
- laggy Camera animations (not very important, maybe it cannot be better),
- high Android OS battery usage (battery really lasts less),
Click to expand...
Click to collapse
+1
Who can tell me how can I put GPS shortcut on quick setting ??I have everything I need except GPS shortcut...
Anyone else have an issue where Calendar just wont sync at all to any Google account? I don't have the options to sync calendars under any of the google accounts I've set up on the device. Tried reflashing, clearing app data etc.
Apart from that, great rom. Super nice battery life.
noponies said:
Anyone else have an issue where Calendar just wont sync at all to any Google account? I don't have the options to sync calendars under any of the google accounts I've set up on the device. Tried reflashing, clearing app data etc.
Apart from that, great rom. Super nice battery life.
Click to expand...
Click to collapse
Clean or dirty install?
By dirty install remove Google accound(s) and then add your accound(s) again.
Worked for me!
For JB4.2 based roms (CM10.1 and AOSP4.2)
if you use a BT headset and are having problems with the mic give this a try.
download the following file.
http://andromadus.flinny.org/libbt-vendor.zip
extract it
Push it to your phone with adb - from the command line
adb remount
adb push libbt-vendor.so /system/vendor/lib
adb reboot
try it now.
Give it a try again and tell me if it all works... If all goes to plan new builds soon
Nick.
Ok folks, this is the only OFFICIAL "What's the best rom, kernel, etc" thread.
This thread will be closely watched by Moderators.
Generally XDA frowns upon threads posted by users asking the same question. It clogs the threads, and makes it more difficult to search.
Please do not abuse this thread.
This IS NOT an off topic thread.
RULES
* Follow XDA rules on posting (abusive, profanity, etc)
* Do not flame other roms and such. Show respect for the people who do the work.
* Opinions are subjective. What you like, others may not. Respect choices.
Enjoy.
MD
Nice thread, maybe you can list what's available (making difference between A700 & A510) splitting by 2 categories : Acer ROM based, AOSP ROM based
Cheers
new user here, so what's the best ROM for A700s? alot of people seem to be on the iconian but it seems the developer is gone, so I guess it should be the cm10.1 version by pawitp?
don't plan to do alot of gaming on it, mainly for magazine reading & web browsing since i've amassed a whole lot of unread zinio magazines which I've subscribed using the free codes they've been generously giving me over the last year.
boringest said:
new user here, so what's the best ROM for A700s? alot of people seem to be on the iconian but it seems the developer is gone, so I guess it should be the cm10.1 version by pawitp?
don't plan to do alot of gaming on it, mainly for magazine reading & web browsing since i've amassed a whole lot of unread zinio magazines which I've subscribed using the free codes they've been generously giving me over the last year.
Click to expand...
Click to collapse
Not sure what happened to vorbeth and iconian. Most of the roms have been around for awhile, and not a lot of issues.
pawitp has the CM which gets updates.
There,s a rootbox version, and Iconian. Iconian runs Acer build.
As with running Acer builds, we're dependant on Acer to push updates, which unfortunately doesn't happen often. However, in my opinion, there's less incompatibility issues with games. Just my opinion. This is why you don't see a lot of updates on the roms. Example, I'll push my first update since release. Audio improvements for folks that appreciate good audio. A little theming, and custom Acer ring.
I'd say flash them all, and see what works best for you. You usually know within a day or so, if you like the rom.
You are right, I flashed them all. Somehow stock is faster than CM & Iconian but your ROM is the best Thanks
I flashed CM10.1.3 RC2 to my A700. Has been working well and I really enjoy the new features I gained coming from stock. Most importantly for me CM gave me a higher touch sensitivity which drastically improved my user experience and was the main reason I switched to CM. It can have some lag tho.
I was thinking about flashing the kiteman V4.1 kernel to see if it helps with the lag, but I need to verify if the "Very High" touch sensitivity option will still be available. If anyone can advise it would be greatly appreciated.
Also, I was thinking about flashing the latest Evil Alex ROM because I have read good reviews. Again, most importantly I need to verify whether touch sensitivity will be increased comparable to CM10.1. Perhaps Moscow Desire or boringest you can inform me?
I would say pawtips' CM 10.2 worked best for me so far. The performance is great and feels far less sluggish than stock, which I had before. Also not having all the branding stuff from Acer also improved the device a lot
mrzottel said:
I would say pawtips' CM 10.2 worked best for me so far. The performance is great and feels far less sluggish than stock, which I had before. Also not having all the branding stuff from Acer also improved the device a lot
Click to expand...
Click to collapse
hi thanks for acer A701 CM 3G enabled ROM..
first i'm installed your rom, mrzottel 10.2 CM Build1 before CM 11 3G enabled.. work great on my acerA701..
then install with pawitp CM 11 after 3G enabled,
my problem after install CM 11..
sometimes my Acer A701 can not wake up from sleep by power button, it must be hardreset with power button.
just like android black screen of death syndrome
Not really sure, but this problem happen after receive automatic update from play store.. downloading apps never finish then A701 frozen when screen off.
(i'm not install fresh apps from playstore, just restore some user apps+data from titanium backup. is it problem?)
dont know what to do. three time or more, try reinstall CM11 rom and gapps, wipe data from CWM 6.0.4.4 and do factory reset
but problem still there..
now i'm back with Build1 atm
Edit:
my acer A701 screen off problem, after install CM 11 with ROM
cm-11-20140112-UNOFFICIAL-3G-a700.zip
MD5-SUM : 26FD6B17954AFE7852C5755871EC4964
today try reinstall ROM with latest Build CM 11 for A700/A701 3G from pawitp thread
cm-11-20140118-NIGHTLY-a700.zip
MD-5SUM : 4265BF680C510DE08C4654A7F1D28DCA
seems my Acer A701 screen off problem fix..
Thanks
i've got the same problem on my A701 i try 2 roms
cm-11-20140121-NIGHTLY-a700
cm-11-20140123-NIGHTLY-a700
any ideas?
melon81 said:
i've got the same problem on my A701 i try 2 roms
cm-11-20140121-NIGHTLY-a700
cm-11-20140123-NIGHTLY-a700
any ideas?
Click to expand...
Click to collapse
i just do some experiment,
replace CM 11 /system/bin/rild with CM 10.2 rild
adding build.prop line with:
rild.libpath=/system/lib/libhuawei-ril.so
rild.libargs=-d /dev/ttyUSB2
one hours trying A701 playing rock music album from Apollo, check on off powerbutton every
5minutes ,
Screen-off problem not occurs yet
but another problem with 3G
*A701 can see network, but 3G Data not connected (3G icon signal bar full)
*set DNS > No network DNS: blank , ip : blank
*wifi works fine
hope someone check CM11 rild file for us A701 users
You should ask @pawitp
Moscow Desire said:
Ok folks, this is the only OFFICIAL "What's the best rom, kernel, etc" thread.
This thread will be closely watched by Moderators.
Generally XDA frowns upon threads posted by users asking the same question. It clogs the threads, and makes it more difficult to search.
Please do not abuse this thread.
This IS NOT an off topic thread.
RULES
* Follow XDA rules on posting (abusive, profanity, etc)
* Do not flame other roms and such. Show respect for the people who do the work.
* Opinions are subjective. What you like, others may not. Respect choices.
Enjoy.
MD
Click to expand...
Click to collapse
Hey A700 users. I'm helping a friend and offered to patch up his A700 from what appears to be stock Android 4.1.1 Build Acer_AV051_A700_1.052.00_PA_CUS1. This does not appear to be the 3G model. I don't see anything in the ROM for mobile networks, and what appears to be the SIM slot next to Micro SD looks like it has a glued in plastic tab in it, not user removable without a bit of force.
So, looks like I need to unlock bootloader, install TWRP/CWM, and choose a ROM which is where my question is aimed. I'm wanting to choose a ROM that is mostly up to date, but also does not have any hardware issues. It appears that CM 12.1 has issues with HDMI which I would like to avoid.
I'm looking for in priority:
1) All hardware working (no workarounds, or other things I need to add as a "if this happens go here and do that" kind of stuff)
2) Stable
3) Up to date.
It appears a lot of ROMs are not seeing much activity which is understandable due to the age of the tablet. I'm keen to just flash this once onto something that is a good daily driver and be done.
After some additional digging I'm thinking about CM11: https://wiki.cyanogenmod.org/w/Install_CM_for_a700
It's strait forward, I know CM well enough....
I still have my old A510 wall mounted for home automation on CM11 4.4.4 . But the problem is that I can not install newer applications. Any way to get newer version of android on it?
FYI, I just installed our last Android 6 build (https://builds.unlegacy-android.org/aosp-6.0/picasso2/) to my A700 that I'm giving to a relative, as I believe it is rather stable. It's the last stable Android version for this device (Android 7+ has various graphics issues), and it uses kernel 3.4. It can be used with an up-to-date TWRP, such as: https://forum.xda-developers.com/t/a51x-a70x-aka-picasso-2-recovery-twrp-3-1-1-0.2678284/.
I'm sure there was a thread for it here, but I just can't find it now...
I upgraded my A700 from latest official CM11 to above mentioned unlegacy build. Unfortunately since then I'm experiencing massive audio distortion so that I had to revert back. Is there anything I missed or anyone with same experience?
Ziyan said:
FYI, I just installed our last Android 6 build (https://builds.unlegacy-android.org/aosp-6.0/picasso2/) to my A700 that I'm giving to a relative, as I believe it is rather stable. It's the last stable Android version for this device (Android 7+ has various graphics issues), and it uses kernel 3.4. It can be used with an up-to-date TWRP, such as: https://forum.xda-developers.com/t/a51x-a70x-aka-picasso-2-recovery-twrp-3-1-1-0.2678284/.
I'm sure there was a thread for it here, but I just can't find it now...
Click to expand...
Click to collapse
I think you should post this on the front page. This is the most up to date rom i can see in the forum. I have installed and its like i have a new device. But your post is hidden away here and i came across is by accident.
bullet157 said:
I think you should post this on the front page. This is the most up to date rom i can see in the forum. I have installed and its like i have a new device. But your post is hidden away here and i came across is by accident.
Click to expand...
Click to collapse
Hi,
Can you share the rom file? The download link is broken ...
Google Drive: Sign-in
Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).
drive.google.com
bullet157 said:
Google Drive: Sign-in
Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).
drive.google.com
Click to expand...
Click to collapse
Would be epic to share this one!! thank you
I didn't realise i could upload files hopefully it works.