Related
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.
Current Changelog below
Checkout http://andromadus.flinny.org for links/files/previous changelogs
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.
Latest version changelog.
CM10 build 133
There was an issue with the backup tool in the last build that will break gapps and your account's etc when flashing this build, the solution is to re-flash gapps at the same time as the rom and you should be fine. This build should fix it so that the next build will work as it should
Changes.
Synced with CM - Again not many changes upstream.
Basically everything relevant to our phones up to the 4th of February in the following has been merged
http://review.cyanogenmod.org/#/q/status:merged+branch:jellybean,n,z
Kernel updated to Andromadus Current - 3.0.62
For any issues you can use the following bug tracker.
http://bugs.andromadus.com/projects/vision-nightly
In the issue please include what version of the test build u are on and if another build gets released please flash and please update the issue saying the bug is still happening on 45 or whatever number.
Howdy.
Sent from my Galaxy Nexus using Tapatalk 2
Just d'loaded. Ill note down the major issues if there are any different from stable B2.
Sent from my HTC Vision using xda premium
cjward23 said:
Howdy.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
YOU!!!!!!!!!!! WHY?!!!!
darkspadez said:
For any issues you can use the following bug tracker.
http://bugs.andromadus.com/projects/vision-nightly
In the issue please include what version of the test build u are on and if another build gets released please flash and please update the issue saying the bug is still happening on 45 or whatever number.
Click to expand...
Click to collapse
Will this cover erectile dysfunction? That kid over there said he never said it had happened before he flashed flinny44..
Because.
Thanks to the andromadus devs for the opportunity!
Sent from my DZ.
So I am assuming there will be no changelog?
I found that this rom is not deodexed ?
shellin said:
So I am assuming there will be no changelog?
Click to expand...
Click to collapse
Correct and also note this comes without warranty. Flinny could post a rom that doesn't even boot. Its basically nightly build of our repos so you can use them without having to build.
So, when's the next one due? Where's the changelog? What's adb? Why would you want a lolcat? ... *snicker*
Just kidding around for a second. I'll flash, follow the updates and post if I find anything suspicious.
darkspadez said:
Correct and also note this comes without warranty. Flinny could post a rom that doesn't even boot. Its basically nightly build of our repos so you can use them without having to build.
Click to expand...
Click to collapse
Great, thanks!
Sent from my T-Mobile G2 using Tapatalk 2
Sup Flinny! /2nd page already
Sent from my HTC Vision using XDA
Unofficial changelog for Flinny44 (from beta2):
Fixed issue where power saving does not work on certain APs under certain conditions causing wifi to drop during sleep without notice. (credit to nyt)
Fixed Keyboard brightness backlight for hidden keyboard
Fixed Camera focus button
Added Statusbar IME Switcher toggle
Fixed speakerphone/on hold/mute issues
Optimized compiler CFLAGS
Russian keyboard fix
Fixed bootanimation resolution
Added camera button play/pause for music when screen is off
Merged in changes for webkit and updated to newest CM repos.
Merged in a whole bunch of camera HAL / qcom changes
Added expanded volume overlay
Those are just things I've been keeping track of, Flinny can expand on the things he's merged in himself
blk_jack said:
Unofficial changelog for Flinny44 (from beta2):
Fixed issue where power saving does not work on certain APs under certain conditions causing wifi to drop during sleep without notice. (credit to nyt)
Fixed Keyboard brightness backlight for hidden keyboard
Fixed Camera focus button
Added Statusbar IME Switcher toggle
Fixed speakerphone/on hold/mute issues
Optimized compiler CFLAGS
Russian keyboard fix
Fixed bootanimation resolution
Added camera button play/pause for music when screen is off
Merged in changes for webkit and updated to newest CM repos.
Merged in a whole bunch of camera HAL / qcom changes
Those are just things I've been keeping track of, Flinny can expand on the things he's merged in himself
Click to expand...
Click to collapse
Thanks for that
Some of those look intresting but sadly I can't be messing around with nightlies..
Posting to feel special
-Nipqer
I havent flashed a rom in a while. Its about that time me thinks, I will let you know if I come across any problems.
Nipqer said:
Posting to feel special
-Nipqer
Click to expand...
Click to collapse
You don't need to post to feel special. Those matter already know how 'special' you are Nipqer
Sent from my Galaxy Nexus using Tapatalk 2
nice
For those that haven't heard already, HTC has released the ICS kernels sources including for the Desire HD!
http://www.htcdev.com/devcenter/downloads
HD are 2.6.35 sources...
tarroyo said:
For those that haven't heard already, HTC has released the ICS kernels sources including for the Desire HD!
http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
After the rather...disappointing way I departed and the resulting issues, I'm setting some things straight here and now.
1. No ETAs. Period. I don't want to see when will I fix or add anything.
2. No complaining. There's a line between reporting an issue and complaining. This line is crossed when it's reported more then once.
3. Requesting additions is fine, within reason. Keep it within reason, I'm not a real dev.
4. Using this ROM...this is where a lot of issues have come up, generally speaking, you can use this ROM as a base if you choose, however ASK ME FIRST. That's it! Everything could have been avoided if people had simply asked me before using my ROM and slapping their names on it then putting it out there. Please include some credit to waydownsouth, gh123man, randomblame and myself. For 4.3 Jellytime, randomblame in particular.
5. Hosting/mirroring. Please don't host or mirror this elsewhere, I will supply hosts for this ROM, I don't need more, and I prefer to keep track of how many users of a given build I have. Hosting elsewhere interferes with this. The only exception I can see is for our Russian/Ukrainian user community, my hosts may be slow there, or in other parts of the world. If you wish to host for another country, please let me know.
6. READ. For the love of all that is holy and great, READ the OPs, read at least the page before where your post will be. I will not answer questions already answered. If I respond, it may not be the nicest way I could do so. Please, save me, yourself, and everyone else the time and /facepalming and at least attempt to find the answer on your own. This is not limited to only this ROM, but anything you may wish to post about in this thread. Questions about CWM or TWRP don't belong here, but if they are valid questions that have something to do with this ROM, go ahead, after reading up on it.
7. Remaining on topic....well this one is loose. I prefer it to stay related only to this ROM, however I know things stray, and generally I'm OK with this, just try to keep it at least related to android. Or at least something related to something to do with on this planet.
Features:
Halo
PIE
Listview Animations (settings>display)
System Settings (CM)
Screenies:
Builds
Jellybean 4.1
Build 1 | Mirror
Kuroikaze-Sosei RC1
Kuroikaze-Sosei II B3 Final
Jellybean 4.3
Jellytime 4.3 - AFH | Jellytime 4.3 - DH
Gapps 4.1
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Gapps 4.3
gapps-jb-20130813-signed.zip
Change log 4.1
Build 1: Updated to 4.1.2 sources. Generally stock CM10. Everything works. I think.
RC1: Based on Black Bean AOSP sources now.
Sosei II B3 Final:
Seeder
AC!D audio
XLoud
Supercharged
Die Hard launcher
init.d memory tweaks
time killer killer mod
maximum overdrive mod
service preserver
transition animations
Final release.
Change log 4.3
Ported from Randomblame's Jellytime Build 7
Build 1: Unreleased, initial trials to get it running. Bootloops.
Build 2: Unreleased, boots, but runs badly, storage is broken, audio stutters
Build 3: Almost everything works now, fixed storage via init/ramdisk entries
FULL WIPE NO MATTER WHAT
Broken in 4.1
RC1 -
Auto Brightness
Hardware Rotation Lock Switch (use software settings, it's more flexible anyways)
GPS
Fixed -
HDMI audio should now work (again)
Switchable UI (tab or phab UIs now)
Bugs-
In tab ui the clock is messing it's rear texture on the homescreen, ie its not black there, its wallpaper instead. Doesn't interfere with anything, just a glitch.
Huge thanks to justjackyl for testing this out for me and reporting back on issues.
FULL WIPE NO MATTER WHAT
Broken in 4.3
Mic
?
Untested:
GPS
HDMI
Bluetooth
Dock
Bugs:
WiFi will not reconnect if it turns off, a reboot is needed. Turning off the always scanning option seems to help this.
Forcing GPU acceleration can help even out the framerate in some cases.
4.1 Instructions:
Root and unlock your device, if you haven't, visit the All things Iconia A100 link in my sig, and read up. Then read again. Then proceed with rooting, unlocking, and installing a custom recovery.
I'm not going to note each recovery's method of installation, hopefully by now you guys know what to do in your recovery of choice.
Download the ROM to external SD
Download a current GApps package to your external SD card. Get one for JB, you can try a 4.2 package, but is as yet unsupported.
Reboot into recovery using whatever method you like:
-Power off then power on holding volume -
-Power menu>reboot>recovery if your ROM supports this
-App from the Play store reboot recovery
Full nandroid backup
FULL WIPE
-Factory reset
-Wipe System
-Wipe Dalvik
-Wipe Cache
Flash ROM (install from zip)
Flash appropriate GApps zip
Reboot system
Let system boot, allow up to 10 minutes for the GUI to come up from the boot animation
After the welcome setup wizard appears, let the tab sit for 10 minutes. Longer is fine.
Reboot tablet
Let sit 5 more minutes
Complete the setup wizard
Restore apps and whatever. Do not restore system apps and/or data
Restore user app data if you wish, but it may cause issues. If problems come up, factory reset and try again without restoring data.
Feel free to flash any kernel you want, but don't post about problems here until you use the kernel it came with first.
4.3 Instructions:
Root and unlock your device, if you haven't, visit the All things Iconia A100 link in my sig, and read up. Then read again. Then proceed with rooting, unlocking, and installing a custom recovery.
I'm not going to note each recovery's method of installation, hopefully by now you guys know what to do in your recovery of choice.
Download the ROM to external SD
Download a current GApps package to your external SD card. 4.3 ONLY! Don't report anything if you use anything but the gapps I linked from my site.
Reboot into recovery using whatever method you like:
-Power off then power on holding volume -
-Power menu>reboot>recovery if your ROM supports this
-App from the Play store reboot recovery
Full nandroid backup
FULL WIPE Don't report ANYTHING if you did not flash 100% clean!
-Factory reset
-Wipe System
-Wipe Dalvik
-Wipe Cache
Flash ROM (install from zip)
Flash appropriate GApps zip
Reboot system
Let system boot, allow up to 10 minutes for the GUI to come up from the boot animation. It may blank out for awhile on the first boot, just leave it be.
After the welcome setup wizard appears, let the tab sit for 10 minutes. Longer is fine.
Reboot tablet
Let sit 5 more minutes
Complete the setup wizard
I strongly recommend you download and install apps FRESH from the Play Store, and do NOT restore apps if possible. If you want, then go ahead...
Restore apps and whatever. Do not restore system apps and/or data
Restore user app data if you wish, but it may cause issues. If problems come up, factory reset and try again without restoring data.
Do not report any issues if you:
Dirty flashed.
Restored anything with any app.
Don't use the supplied kernel.
Modified the ROM in any way prior to the issue coming up.
Did not read the entire post and noted what bugs are already known to exist.
Did not use the 4.3 GApps on my site which I linked right below the ROM download.
Can not report a bug issue without quoting Hawkeye because you skipped all of this.
Thanks:
waydownsouth
randomblame
gh123man
godmachine / linux society
justjackyl
das_webos_transformer / xbooow
Cyanogenmod
AOKP
Team Baked
The Team behind the AC!D audio engine
Plus more, I'm sure.
HOLY SANTA CLAUSE ****!!!!!
CM9 Nightlies, Custom ROM, Rooting/Flashing Kit and "how to" tutorials
If there is anyone in the A100 community the deserves a donation it's this guy!
cdkg said:
HOLY SANTA CLAUSE ****!!!!!
CM9 Nightlies, Custom ROM, Rooting/Flashing Kit and "how to" tutorials
If there is anyone in the A100 community the deserves a donation it's this guy!
Click to expand...
Click to collapse
Roflmao so says my biggest donater!
Sent from my SGH-T989 using Tapatalk 2
You are the freaking man!
Sent from my A100 using xda app-developers app
Go for it.
You sir, are why I miss my Iconia A100 . Hopefully can get a new one soon, miss the A100 community
Sent from my SCH-I500 using Tapatalk 2
A big thank you !!!!!!!!!!!!!!!!!!!!!
So I got myself an A100 from ebay for 140 bucks just to toy with it and find its relevant thread on XDA to flash me some cm9 and what do I see. Working jb port completed already.. Imagine my shock !!!!! Hail *pio_masaki* .... you are the Man dude !!! :angel: Any amount of compliments I make is just insufficient to praise the amount of hard work and time you put behind this. :good::good::good::good: Just flashed v5-2 already and its "butter" smooth operation from then.. Wait till I show this to my friends...
rockthegod said:
So I got myself an A100 from ebay for 140 bucks just to toy with it and find its relevant thread on XDA to flash me some cm9 and what do I see. Working jb port completed already.. Imagine my shock !!!!! Hail *pio_masaki* .... you are the Man dude !!! :angel: Any amount of compliments I make is just insufficient to praise the amount of hard work and time you put behind this. :good::good::good::good: Just flashed v5-2 already and its "butter" smooth operation from then.. Wait till I show this to my friends...
Click to expand...
Click to collapse
Thanks, and welcome to our little corner of XDA! Hope your new tablet is as good as mine has been to me
But really guys, randomblame did the hard work on this. I just got it running on the A100.
Pio, I know the feeling on the time spent on these things and friction with the wife. Use lube, Red Wine is what I suggest, good for the heart.
Jk buddy, thanks for all your work and time. Family first. We understand.
wild1z said:
Pio, I know the feeling on the time spent on these things and friction with the wife. Use lube, Red Wine is what I suggest, good for the heart.
Jk buddy, thanks for all your work and time. Family first. We understand.
Click to expand...
Click to collapse
Thanks for the understanding.
Also....new version with WiFi and some sound is up. Root seems to work to a point but I'll say its broken for now.
tapatalked from my A100 - Jellytime V7.7
unbelievable, I am bewildered by this topic! fantastic!
Pio_masaki,I have been a silent observer of your threads for quite a while, and I have to say that I have never seen such a nice person as you. Maybe there're other developer in XDA that has a better skill than you (just maybe, haha, please don't be offended =p), but regarding personality and character, I think no one can match you. You really deserve the best person award. Thanks for all the work that you have done to the community =)
xitrumch said:
Pio_masaki,I have been a silent observer of your threads for quite a while, and I have to say that I have never seen such a nice person as you. Maybe there're other developer in XDA that has a better skill than you (just maybe, haha, please don't be offended =p), but regarding personality and character, I think no one can match you. You really deserve the best person award. Thanks for all the work that you have done to the community =)
Click to expand...
Click to collapse
Thank you for the kind words, and no I'm not offended, there are certainly much better developers for sure, as I don't really consider myself a developer anyways. Most of this work has been done by randomblame and waydownsouth I just move it over for us on the A100, which isn't always easy I'll admit.
Version 7.8 is now available
Change log:
Root is now working as it should.
Open Super SU
Let it "install" binary (its already there)
Enjoy
External SD is now RW:
Fixed a permission issue in platform.xml to allow full read/write to external_sd.
Brightness control now works:
Auto brightness doesn't seem to work, manual brightness works. This was actually fixed in a previous release, and broke again, and is now working again.
Sound:
Sound works in some apps, but system sound is still broken, ie notifications, music, but some apps/games work, like angry birds now has audio.
Bluetooth:
Bluetooth has been proven fixed by a pairing, testing done by ntan97.
Still Broken:
Gallery/camera
Internal SD doesn't mount
Power LED is erratic, sometimes always on, sometimes always off
Home to wake: works when power led is ON, doesn't work while it is OFF
Video playback is still broken. Tested on stock player, dice player, mp4 and avi.
I'll be redoing the posts to be a little less confusing by moving things to change logs like this.
Wow man. I'm surprised on how much progress you're making on this. It's quite a feat. You can say all you want about how you're just compiling what others have made to the A100, but it takes a good person to continue a project for such a small community like this (even after you said you were going to slow down? I haven't seen you slow down at all) and it's still not just that simple.
You're probably one of the most helpful people here since crossix. Thanks for you're work :thumbup:
Hopefully when I receive a new PC in a couple weeks I could start making the first complete A100 theme for this ROM. To my knowledge there really hasn't been a whole lot of action in the themeing department here.
Sent from my A100 using Tapatalk 2
notsointeresting said:
Wow man. I'm surprised on how much progress you're making on this. It's quite a feat. You can say all you want about how you're just compiling what others have made to the A100, but it takes a good person to continue a project for such a small community like this (even after you said you were going to slow down? I haven't seen you slow down at all) and it's still not just that simple.
You're probably one of the most helpful people here since crossix. Thanks for you're work :thumbup:
Hopefully when I receive a new PC in a couple weeks I could start making the first complete A100 theme for this ROM. To my knowledge there really hasn't been a whole lot of action in the themeing department here.
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
Yeah....I keep saying ill slow down.....then I get a new idea or theory and go back until I get it right lol
Theme wise stetsonaw has a complete theme that works for us, but of course more is always better, I'm partial to black and red myself.
And PC...yeah don't get me started on that. My fastest machine takes 3 hours to build. That's like 2 hours of prepping 3 hours to build just to test. Unless its something I can do after compiling. That's the version number, first is build second is changes within that build after its built. So current is build 7 change 8, so figure 3 hours per build, plus whatever time of work before the build, plus whatever hour so per change after... plus the builds I didn't even number lol.
All said and done I have at least 21 hours invested in builds. Probably another 15 in smaller revisions, plus the 9 hours getting the initial port worked out. Over...maybe 2 or 3 weeks. Plus the nightly cm9 builds. And a few hours for the scripts, few more for aoikaze, and more on kuroikaze which I'll likely never finish and release. Oh and the guides lol.
It adds up quick. This is just since May...I think closer to June when I started all of this.
Edit: Just realized I have over 99 hours in the nightly cm9 builds, not counting setting up for it and uploading time lol
tapatalked from my A100 - Jellytime V7.9
I just flashed and have noticed one thing (I apologize if already stated just haven't seen)
But it looks like just a density issue. Fonts are just small at times. The stock launcher seems a little weird and when in landscape the notification bar is far on the left.
I tried my best to take a photo.
And just a question. Are their specific 4.1 gapps or are the ICS ones the same?
You can follow me on Twitter - @NotSo1nter3stin
notsointeresting said:
I just flashed and have noticed one thing (I apologize if already stated just haven't seen)
But it looks like just a density issue. Fonts are just small at times. The stock launcher seems a little weird and when in landscape the notification bar is far on the left.
I tried my best to take a photo.
And just a question. Are their specific 4.1 gapps or are the ICS ones the same?
You can follow me on Twitter - @NotSo1nter3stin
Click to expand...
Click to collapse
Yeah not a bug, that's the new 7" UI jellybean uses. Not sure why they killed the combined bar and chose a phone UI though. That's how the N7 will look too.
Oh edit there is a jb gapps but they're kinda broken, so flash them, ten icss gapps over it and itll work, that's how I do it. I'll add them into the OP sometime today, niece and nephew are staying with us for a few days so I'll be busy being the coolest uncle ever with all my modded consoles, devices and toys lol
tapatalked from my A100 - Jellytime V7.9
pio_masaki said:
Yeah....I keep saying ill slow down.....then I get a new idea or theory and go back until I get it right lol
Theme wise stetsonaw has a complete theme that works for us, but of course more is always better, I'm partial to black and red myself.
And PC...yeah don't get me started on that. My fastest machine takes 3 hours to build. That's like 2 hours of prepping 3 hours to build just to test. Unless its something I can do after compiling. That's the version number, first is build second is changes within that build after its built. So current is build 7 change 8, so figure 3 hours per build, plus whatever time of work before the build, plus whatever hour so per change after... plus the builds I didn't even number lol.
All said and done I have at least 21 hours invested in builds. Probably another 15 in smaller revisions, plus the 9 hours getting the initial port worked out. Over...maybe 2 or 3 weeks. Plus the nightly cm9 builds. And a few hours for the scripts, few more for aoikaze, and more on kuroikaze which I'll likely never finish and release. Oh and the guides lol.
It adds up quick. This is just since May...I think closer to June when I started all of this.
Edit: Just realized I have over 99 hours in the nightly cm9 builds, not counting setting up for it and uploading time lol
tapatalked from my A100 - Jellytime V7.9
Click to expand...
Click to collapse
Bit off topic... but woah, thanks man. Just donated 5€
Please note, I'm retired, and for the most part I don't visit XDA very often, I will respond if I happen to notice there's been a post, but don't send me angry PMs if I don't, personal life and finances has made it almost impossible to continue my work with android at all.
That being said, I'll still help where and when I can.
First and foremost, this is based on waydownsouth's trees, both the T20-common and the A100 specific trees with some updates and changes and additions from me.
I can't test anything, I don't have an A100.
These are not going to be nightly, daily, weekly, or whatever, these are now simply where I post test builds from working on the trees.
These are 4.1.2, and NOT 4.2! Use the 4.1.2 GApps packages!
Since I'm starting over, there are things that NEED to be tested, please:
BlueTooth
GPS
WiFi
Audio in general/performance
Audio specific outputs/inputs, such as headphones, headsets, BT, HDMI, dock, USB, whatever you can think of.
Video playback support/performance
Mounts, internal, external, swapped, whatever.
UI performance, I don't mean "It has a slight stutter for 1/4 of a second scrolling my 500 apps app drawer 2 seconds after it booted" I mean it either runs well or runs like crap over a day or two of use.
Cameras. I mean cameras in normal designed use, not photosphere or why it won't take clear pictures underwater at 8mp from the front camera.
Whatever else you can think of that needs testing
Please report them here, this is to take the random stuff out of the trees thread and keep here where it's more relevant.
As usual right off Hardslog has permission to use these as bases for whatever he wants, in a pinch, he can use them for toilet paper, anyone else please ask or let me know first.
Instructions
Coming from a previous pio_masaki build:
Make a nandroid backup of your current install, backup system, boot and data. Recovery optional.
Wipe Cache
Wipe Dalvik Cache
Wipe System
Install from zip (cwm) or install (twrp) and pick the cm10 zip you want.
CWM:
Hit yes (cwm)
Flash Gapps (cwm) *use a 4.1.2 GApps, not a 4.2 GApps*
TWRP
Hit the additional zip button, add gapps zip *use a 4.1.2 GApps, not a 4.2 GApps*
Slide to flash
Both
Reboot
Let ROM sit for 10 minutes
Reboot
Let ROM sit for 5 minutes, begin normal usage.
Coming from any ROM besides a pio_masaki CM10
Make a full nandroid backup
Wipe Cache
Wipe Dalvik
Wipe System
Factory Reset (optional, blackhole wipe, this will wipe internal SD as well!)
Install from zip (cwm) or install (twrp) and pick the cm10 zip you want.
CWM:
Hit yes (cwm)
Flash Gapps (cwm) *use a 4.1.2 GApps, not a 4.2 GApps*
TWRP
Hit the additional zip button, add gapps zip *use a 4.1.2 GApps, not a 4.2 GApps*
Slide to flash
Both
Let ROM boot, allow for up to 15 minutes.
Once the welcome screen appears, let it sit for 10 minutes. Don't do setup yet.
Reboot
Let sit 5 more minutes.
Proceed with setup wizard
Restore USER apps only. Restore data if needed, otherwise start fresh from the Play Store.
DO NOT RESTORE SYSTEM APPS OR DATA
Reboot after restore is finished.
Use as normal.
Downloads
Ok, goo.im went down, and pio-masaki.com is gone, so the files are effectively gone for ever. I have 1 single build, B3 TabUI Mod, which you can find here:
CLICKY CLICKY
Also a far older, dusty, ancient build is tucked away over on devhost, which is here:
GRANDMA CM10
I have no idea what works or doesn't with it.
If those don't float your boat, head over to the kuroikaze thread, there's some builds there as well, 4.1 and 4.3 based.
Feel free to use any gapps packages you wish, but please use 4.1, if you have issues with things like keyboard vanishing/crashing, play store or other stuff crashing, these ARE gapps related.
Change log:
B1 - 11-08-12: Initial updated 4.1.2 build. Addressed HDMI audio. Memory bar added to recent apps.
B2 - 11-25-12: Updated source build. Memory bar in recent apps removed, "kill all" button added to recent apps instead, upstream CM change.
B3 - 1-13-13: Updated source, built using Linaro 4.7 toolchain and -O3 and strict-aliasing in various areas. ROM only, kernel is still stock CM9. Basically just an updated build for you guys, haven't addressed anything in particular.
B3 - 1-13-13 Modded:
Acid Audio with Sony and Awesome Beats, new transition animations, slight dalvik tweaks. Just some of the stuff I've been working with on the Thrive added in for flavor. Untested.
B3.5 - 1-17-13: Updated source to B3, however is built with Tablet UI forced, otherwise stock build of CM10, no mods. Don't expect me to keep doing dual builds of CM10 for you guys =p
B3.5 Modded - 1-17-13: Updated source to B3, however is built with Tablet UI forced, same mods as B3 Modded.
B4 - 1-19-13: Addressed GPS issues, Trebuchet oddness and clock fitment (cutoff). Blind fixes, may fix everything or nothing.
B5 - 2-01-13: Nothing special, just an updated build as was asked about. Here's your friday night flash fix guys. Apparently broke external SD mounts somewhere.
B3 Tablet UI and B4 Phablet UI:
Seeder
AC!D audio
XLoud
Supercharged
Die Hard launcher
init.d memory tweaks
time killer killer mod
maximum overdrive mod
service preserver
transition animations
20130715
Updated source
Trimmed the trees a little
Added prebuilt kernel and modules
Simply a test build that the changes didn't break anything.
20130731
Experimental 3G/RIL support for A101 devices!
Memory management, in a couple places now, to help with memory leak issues. While it may not prevent the memory leaks, it should prevent it from impacting the system so badly. Thank you, nVidia.
Dock settings added for those with the dock. Does anyone even have one?
BT DUN, WiFi P2P and WiFi Direct support added (experimental)
Rotation Lock Switch support added (back) in
Music Visualization overlay settings
Add large heap to launcher2
Tuning of the boardconfig and device files for UI.
Probably more I'm forgetting.
20130801:
Paths in init corrected, should fix mount issues from B5 to now.
Lockscreen rotation enabled even with switch in use by the ROM in overlay.
20130801-B2:
Redid init, should all be peachy again.
20130802:
Once again massive battles for no real obvious reasons besides I'm getting rusty.
Internal SD workd as it should
External SD works as it should
USB Storage ability added
Settings>Storage crash corrected, no longer force closes
Should now be back to a daily driver usable status, so please do further testing on audio, etc and report back your findings. @hardslog, this update may finally be good enough for an updated base lol
20140404:
Updated source
Trees are 99.9999% the same as last build, with one change:
Remove unsupported overlay
Won't, or shouldn't, have any apparent changes.
Built on request from our Russian cousins.
Thanks:
waydownsouth - for working with me enough to even begin to comprehend what he's done for the Iconia devices.
randomblame - for helping me getting jellytime up on the A100 and helping me out with random ideas and interesting conversations in IRC.
ntan97 - being my tester in IRC for the most random ideas I've ever had.
justjackyl - for being my go to guy for testing anything I do for the A100.
Cyanogenmod - for obvious reasons.
Google - for obvious reasons.
The team behind Acid Audio
The guy(s) behind Awesome Beats
Everyone who's donated, its appreciated
I'm sure I missed some, if I did it's nothing personal.
Hey pio_masaki,
I don't know what it takes to build a rom, but I have an A100 and would like to see this thing get some good 4.1/4.2 action going. I'm alright with a command line and I actually do QA for web programmers for a living. And I really want to learn more about android.
If you build em, I can test em and report back. On this CM10 build or your Jellytime Sosei. What do you think?
kiden said:
Hey pio_masaki,
I don't know what it takes to build a rom, but I have an A100 and would like to see this thing get some good 4.1/4.2 action going. I'm alright with a command line and I actually do QA for web programmers for a living. And I really want to learn more about android.
If you build em, I can test em and report back. On this CM10 build or your Jellytime Sosei. What do you think?
Click to expand...
Click to collapse
4.2 will not be an option from me, I don't have an a100 to even get it booting. Secondly, I don't feel like building a new twrp to handle an android version that may never be used on this device. Again, maybe if I had one, but its not worth the extra hassle right now.
Sent from my Thrive - Kuroikaze B18 - Balthesaur V2.71b
pio_masaki said:
4.2 will not be an option from me, I don't have an a100 to even get it booting. Secondly, I don't feel like building a new twrp to handle an android version that may never be used on this device. Again, maybe if I had one, but its not worth the extra hassle right now.
Sent from my Thrive - Kuroikaze B18 - Balthesaur V2.71b
Click to expand...
Click to collapse
Well if you want help with testing the 4.1 builds, I'd be up for it.
Have no fear
if you build it I'm gonna use it (ics or jb} am right proud of your work and enjoy using it.. thanks alot:good::good::victory:
Now I'm torn between this and Sosei.
I got Sosei exactly how I wanted, but I'm a junky for updated source as well.
Sent via Jellytime Sosei Bakedbean Iconia A100.
justjackyl said:
Now I'm torn between this and Sosei.
I got Sosei exactly how I wanted, but I'm a junky for updated source as well.
Sent via Jellytime Sosei Bakedbean Iconia A100.
Click to expand...
Click to collapse
I hear that
Sent from my vangogh using Tapatalk 2
billypoke said:
I hear that
Sent from my vangogh using Tapatalk 2
Click to expand...
Click to collapse
That's the beauty of a Nandroid!
Sounds like I need to stop making more then one ROM for you poor users
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
Sounds like I need to stop making more then one ROM for you poor users
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Lol nah
That's OK, you dev to your hearts content.
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
justjackyl said:
Now I'm torn between this and Sosei.
I got Sosei exactly how I wanted, but I'm a junky for updated source as well.
Sent via Jellytime Sosei Bakedbean Iconia A100.
Click to expand...
Click to collapse
Yeah same here. Nandroid will help me decide and I can switch back if need be.
Sent from my A100 running Jellytime Sosei Bakedbean using xda premium
pio_masaki said:
Sounds like I need to stop making more then one ROM for you poor users
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
B-b-but I like having choices!
Sent from my SCH-I535 using Tapatalk 2
First off thanks pio for making yet another rom for our device. I was able to load this up before work and play with it for a few minutes. It seemed very smooth and responsive. Two minor things I noticed 1.The bottom part of the clock was cut off in the status bar even when I expanded it and it happens in landscape and portrait 2. When switching apps in portrait mode the top 75% of the screen is grayed/dimmed for the background but the bottom is still normal. Unlike in landscape were the whole background is grayed/dimmed.
Neither of these issues are serious or deal breakers though just a couple minor things I noticed.
If this sounded confusing I will try to attach some screenshots when I get home.
Once again thanks Pio.
Sorry to ask, but must i flash b2 over b1 or can i just flash b2. Coming from a different rom.
rain987 said:
Sorry to ask, but must i flash b2 over b1 or can i just flash b2. Coming from a different rom.
Click to expand...
Click to collapse
You don't need to go in order, but follow the directions for coming from another ROM. In short, full wipe.
Sent from my Galaxy Nexus using Tapatalk 2
Battery... why are you always so low when I find delicious new builds...
Thank you from the bottom of my heart ..
nsmith4 said:
First off thanks pio for making yet another rom for our device. I was able to load this up before work and play with it for a few minutes. It seemed very smooth and responsive. Two minor things I noticed 1.The bottom part of the clock was cut off in the status bar even when I expanded it and it happens in landscape and portrait 2. When switching apps in portrait mode the top 75% of the screen is grayed/dimmed for the background but the bottom is still normal. Unlike in landscape were the whole background is grayed/dimmed.
Neither of these issues are serious or deal breakers though just a couple minor things I noticed.
If this sounded confusing I will try to attach some screenshots when I get home.
Once again thanks Pio.
Click to expand...
Click to collapse
I can confirm this report about the UI, it looks as though it is out of scale (status bar, notification bar). What I'm guessing is another side effect of this is that when you hold Home and slide up to open Google search, the Google Arc and button are offset about 150 or so pixels to the left.
Also, I'm experiencing that the back button becomes slightly unresponsive after a while, this can be fixed by going to CM Settings > Navigation Bar > Reset to defaults.
Guys reporting random bugs is really quite pointless, I can't fix what I don't have. These are basically a nightly cm10 build to keep you guys updated, I can't test or fix anything wrong with them, I don't have one.
Sent from my Galaxy Nexus using Tapatalk 2
Un-Official Evervolv AOSP
This ROM is still in testing phase but must say it works quite nicely. Most all features are working fine. Read below for description of ROM.
As you may or not know, Evervolv has been building quality AOSP for multiple devices. Recently we (Classicnerd) have had the pleasure of working with Preludedrew in testing, working out bugs, and joining together to bring a fantastic rom to everyone using HTC, HP Touchpad, Samsung, Asus Nexus 7, and many more devices.
What to expect? Expect a solid platform which to build from. They have been known for adding Evervolv Toolbox which allows status bar tweaks, interface tweaks (volume wake, volume music control, Custom display density settings, and customizable power menu settings), as well as a stable platform which we can bring this hardware to full usage. There is also a Performance section for memory management and processor changes. The Themes section in settings is not working but should be very soon. Su works fantastic and so does the 4-1 boot to recovery work flawless.
Why Un-Official? There are many bugs to work out in an AOSP ecosystem. With that said, these bugs won't hinder your ability to enjoy this great device what so ever. Mostly when people go to an official release, it's because all hardware and software function as if it was stock with no issues and then they move on to the next build (possibly the next update). As you all know, there will always be some sort of issue. But we have a slight advantage with the Nexus 10 device. It's straight up Google. With Google in full support of the Android Open Source Platform, this gives many developers the opportunity to bring customized settings, tweaked apps, and modded framework to bring to the general public and flashaholics something we felt the direction should go.
Now we give you Evervolv Stella. I will let you all guess why the name stella came about. hehe, it was chosen by me which I feel honored to help support this project for you guys. Please understand that everyone on this team have full time jobs as well as work countless (often unappreciated, but more often appreciated) working on source code to bring ideas to life, while having a family life. If you feel the urge to donate, please do. We are saving to bring a Nexus 10 to Preludedrew. His wife cut him off from spending money on devices...lol No worries, we'll get him one.
This ROM ROM is very fast and smooth. While there may be glitches associated with jb, they are being removed and pushing it to the limits.
We now bring you Stella
Release date 11/26/12
* init.d scripts to boost performance, battery, low men, net boost, trim, and much more
* Ramdisk mods
* quad scores above 5300
* BT file transfer for all file formats
* 4-1 boot menu
* Updated to 4.2.1
* Inline Kernel Build
* Fixed YouTube
* EVToolbox
* All Hardware functional
* Google backup support (flash GAPPS after flashing rom)
* Google locations support
* OTG support
* SU working properly
* And many source mods coming from ICS
What doesn't work:
* themes
* you tell us....we need ur help bring this rom to life.
Downloads:
Stella v3.2.0 b4 Un-Official Updated 2/16/13 to 4.2.2
Stella v3.2.0 b3 Un-Official Uploaded 12.06.12 with google locations fixed.
Stella v3.2.0 b2 Un-Official Uploaded 11.27.12
Stella v3.2.0 b1 Un-Official Uploaded 11.26.12
Gapps JOP40C
With many thanks to Evervolv (Preludedrew, drewis, MongooseHelix, and nikez), tommytomatoe, misfit, ewalk, MindSplit, Jzen, Chubbzlou, TMartin, MYN, Cyanogenmod, XDA, craigacgomez, our wives and children, and the many testers. This list will grow as time evolvs..
Evervolv Source Link
AOSP Download AOSP Link
Installation directions.
1) You need to be unlocked and rooted. If you don't have either, check out the Nexus 10 android developement section for many different ways to prepare you device.
2) Copy the ROM and GAPPS packages to your Download folder on your Nexus 10
3) Boot to recovery and factory reset your device
4) Flash ROM
5) Flash GAPPS
6) Boot and enjoy
If updated from previous installation of the Evervolv Rom, installation is much easier.
1) Boot to recovery
2) Wipe cache
3) Flash Rom
4) Flash GAPPS
5) Reboot
6) Enjoy
un-official mods and add-ons
Awesome!! And first!!
Sent from my Galaxy Nexus using xda app-developers app
darkstar765 said:
Awesome!! And first!!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Haha, you're in for a treat. Sucks it takes so long to upload. But, only 22 minutes left till we go live
Edit...just two minutes left
I think this is also a good ROM.
ok, Rom and GAPPS are uploaded
Looks great! I'm about to try. Thank you!
@Leoisright nice... good to see Evervolv here... used to use this on my Nexus One... my brother still does on his!!
This device is going to have the best ROMs... CM, AOKP, Evervolv & Paranoid are already here and it's been just a week!!!
i know, all the big dogs in the house. Ur rom is great tho. It held me over until we got this rolling. I know it's priority #1 to get the kernel inline due to the mods in settings to OV/UC and mess with some other settings too. Once we get it right, you'll be the first to see the changes.
I have a few things i'll show you to add some stuff if ur interested. only little things but good ones. After I get this all set up i can show you.
HuluPlus and Youtube are not functional. Love the speed and smoothness though:thumbup:
†††
FL0OD said:
HuluPlus and Youtube are not functional. Love the speed and smoothness though:thumbup:
†††
Click to expand...
Click to collapse
ok, great...didn't test either of them. will check out the issue
Leoisright said:
i know, all the big dogs in the house. Ur rom is great tho. It held me over until we got this rolling. I know it's priority #1 to get the kernel inline due to the mods in settings to OV/UC and mess with some other settings too. Once we get it right, you'll be the first to see the changes.
I have a few things i'll show you to add some stuff if ur interested. only little things but good ones. After I get this all set up i can show you.
Click to expand...
Click to collapse
Sounds good...
I was actually working on some of this stuff for my Galaxy Nexus and when I got my device I just built it from AOSP and slowly added a few basic things... I just learned a lot of this stuff a few months ago with my Transformer Prime... so I'm still pretty much a newbie!
craigacgomez said:
Sounds good...
I was actually working on some of this stuff for my Galaxy Nexus and when I got my device I just built it from AOSP and slowly added a few basic things... I just learned a lot of this stuff a few months ago with my Transformer Prime... so I'm still pretty much a newbie!
Click to expand...
Click to collapse
do you have app compatibility issues with ur rom? Ours isn't compatible with basic ones like dropbox, youtube, rootexplorer, etc
Yeah, i jumped head first in aosp about a year ago. be very carefull, it can burn you out...lol i had to take a couple months off and enjoy other people work before i wanted to do it again.
Did anybody lose root after flashing this rom? And Google Now won't run because of Location setting problem.
Itaintrite said:
Did anybody lose root after flashing this rom? And Google Now won't run because of Location setting problem.
Click to expand...
Click to collapse
i didn't loose root. Sounds strange, but check the time settings. Mine changed to 6 hours ahead the first time i flashed it
edit. my root is fine, but there is something messed up with location. I can fix that in the next update.
Leoisright said:
i didn't loose root. Sounds strange, but check the time settings. Mine changed to 6 hours ahead the first time i flashed it
edit. my root is fine, but there is something messed up with location. I can fix that in the next update.
Click to expand...
Click to collapse
Weird. I ran root checker and confirmed that device isn't rooted. Came from PA-2.99.3.
click on settings/toolbox/interface/change dpi by 1. you will see it takes root privies. If not, something else may be going on. let me know if you could. also, open superuser. mines shows the pasted two days of usage.
Leoisright said:
click on settings/toolbox/interface/change dpi by 1. you will see it takes root privies. If not, something else may be going on. let me know if you could. also, open superuser. mines shows the pasted two days of usage.
Click to expand...
Click to collapse
You're right. But doesn't work with any other app that requires root. I just tried Adaway and it failed.
Itaintrite said:
You're right. But doesn't work with any other app that requires root. I just tried Adaway and it failed.
Click to expand...
Click to collapse
ok, will add it to the list. I know drewis just updated it and will report the bug
thanks for letting me know. There is an apparent compatibility issue as well. Will get that fixed too.
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
Hi Flinny, great job on the AOSP builds they are running perfect. I only had one satback sins build 4. Suddenly my gallery stopt working and dropbox to. Because of the gallery problem my camera won't boot either. I flashed build 5 but I had the same problem. Build 4 was flashed with a full wipe and build 5 was flashed as update that the reason of course why the problem didn't left but sometimes it helps Does this sound familiar? Greetz Munky
I tested it last evening but have many FC message about "aosp keyboard" even with the physical keyboard
I wiped all but still the same message going back to cm10.1
Ok I'm a little rusty on the details at the moment but: AOSP means that you want it to get as close as stock experience as you can get right? (I'm really looking for a G-lite thing but then with ICS/Jelly Bean, sort of Nexus feel but then for our Desire Z)
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Sent from my HTC Vision using xda app-developers app
I know that this is a dumb question and the answer is probably within the other thread, but... Ah heck, now it's just that I'm too lazy to look for the solution LOL...
But I installed AOSP 4.2 v6 last night and so far I'm not experiencing any major problems (except for FCing when I edit a picture and a bit of confusion adjusting to some new features LOL)... But when is this project going to be merged with CM? There are LOTS of creature comforts (e.g. silence during night hours, T9-style contact search, etc.) that I'm used to with the CM-optimized version that I kinda miss and only noticed that it was gone when I flashed it (I was under the impression that those features were all standard?)
Sorry to pester and thanks in advance.
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Eddy130306 said:
What's everyone's opinion on these AOSP builds? To me they seem more stable and faster than CM. I kinda miss CM a little though, but not the lag.
Click to expand...
Click to collapse
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
google ears
EDIT: Sorry wrong thread
BTW: how can I delete my post?
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
zofox said:
I can't find changelog in your site flinny can you link it ?!
Inviato dal mio HTC Vision con Tapatalk 2
Click to expand...
Click to collapse
http://andromadus.flinny.org/?q=node/2
This is absolutely the smoothest 4.0+ ROM I have ever used. Might switch to CM10.1 though for more features.
adamz667 said:
EdWaRdW818:
Here you've got CM10.1 which is based on AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=2031678
Flinny:
Could you add init.d support to the rom or fix it? I see that there is a placeholder for scripts and there is one script, but it's not executed on boot (with 755 permissions).
Click to expand...
Click to collapse
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
Oh jeez... Either I had a total brain fart and completely missed the link or it got posted anywhere from the time I posted it to the catching up of 14+ hours of sleep (I only slept 7 hours across 3 days LOL), but I guess CM10.1 is already posted. I'll download it and see what's up. Thanks for not flaming me guys. I would've gotten the N4 but I'm not a big fan of LG (had countless bad hardware experiences) and my phone is somewhat last on my "to upgrade list", so thanks for everybody's help and keep up the good work! There's some top quality Münchner Bier mit your name on it once I get some disposable income
catachresistant said:
Have you tried Flinny's CM 10.1?
(I haven't - I'm just curious as to what you think)
Click to expand...
Click to collapse
No I have not.
Sent from my HTC Vision using xda app-developers app
---------- Post added at 02:11 PM ---------- Previous post was at 02:00 PM ----------
LAMER_CZ
That is strange. Which recovery are you using? Don't use clockworkmod as they're always full of glitches and bugs. Don't use ROM Manager to flash ROMs either as they as well have glitches. I recommend doing everything in recovery. If you do have clockworkmod I recommend flashing 4ext as it has more features and can make your phone a little faster
Sent from my HTC Vision using xda app-developers app
Ok I just went ahead and installed it. This is exactly what I need for a ROM on my Desire Z! Thanks Flinny, and keep up the good work!
Now my experience with this ROM:
- I just fly trough my home screens and menu's, it runs fluently!
- When at stock speeds (so 1Ghz) I sometime run into problems booting up the settings. I just hangs there for 4+ seconds untill it actually shows the settings. Setting clockspeeds to 1,8Ghz fixes this most of the times, but it's something you might want to look into (Or don't, it's your ROM)
- The above also happens with some apps.
I don't run swap or any other optimization, so I don't know if it's my problem or a ROM problem, but if you want me to do some more testing just tell me what I need to do
Boot Loop
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
usc911 said:
Thanks for the work, this is a great ROM, just thought I would pitch my issue I had.
Im currently testing an app and set the device to use 2g only as I wanted so see how quickly it pulled in my data on a slower connection. If you leave it in 2g mode and reboot it appears to get stuck in a boot loop.
Hope this is helpful.
Cheers
Click to expand...
Click to collapse
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Authorita said:
I doubt that has anything to do with the "2g" setting since the radio doesn't come on until after it is booted up. Maybe that application you're testing screwed something up?
Click to expand...
Click to collapse
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
usc911 said:
The app is fine, I have been building it for a few weeks and runds fine on a nexus one, and a sapphire. I have tried flashing the 4.2.1 AOSP build and the CM10 build and exactly the same is happening.
Guess I'm just missing something :s
Click to expand...
Click to collapse
Do you think you could get a log of the reboot? Might help in figuring out why it is rebooting like that.