Hey there!
i'm pretty new to modding android and recently got an A101 from a colleague - i think still one of the two best devices in the 7" format with only the Huawei Medipad providing the same functionality.
Anyway, i'd love to try something new and am already rooted with ZeroNull's method wich worked like a charm. Now that i've read many threads in this forum the past week i'm a little bit concerned about some things. First of all, when i'm in stock recovery my power button isn't working, so i cannot make any input besides selecting the menu-entries. Is it likely the case, that i would be facing this issue when installing a custom recovery? Since TWRP has a touch gui i shoudn't be aware of this, right?
Further A101 specific questions i wanne be 100% sure of, since there's no A101-Forum:
- i'm fine with installing bootloaders like TWRP or CWM made for the A100?
- aswell ZeroNull's unlock bootloader method?
- which custom ROM's do support 3G? I'm thinking about pio_masaki's Jellytime Sosei, his CM10 build, or KEBBERSROM...(?)
rather an ubuntu related question:
Am i fine with installing the packages: android-tools-adb & android-tools-fastboot or do i need the full - Android-SDK?
The most important thing for me is to get rid of acers bloadware, so i'm planning to install TWRP followed by a nandroid backup and kiling them softly *fingerscrossed*
running StockRom: Acer_AV0141_A101_1.015.00EMEA_DE
VolkerPfosten said:
Hey there!
i'm pretty new to modding android and recently got an A101 from a colleague - i think still one of the two best devices in the 7" format with only the Huawei Medipad providing the same functionality.
Anyway, i'd love to try something new and am already rooted with ZeroNull's method wich worked like a charm. Now that i've read many threads in this forum the past week i'm a little bit concerned about some things. First of all, when i'm in stock recovery my power button isn't working, so i cannot make any input besides selecting the menu-entries. Is it likely the case, that i would be facing this issue when installing a custom recovery? Since TWRP has a touch gui i shoudn't be aware of this, right?
Further A101 specific questions i wanne be 100% sure of, since there's no A101-Forum:
- i'm fine with installing bootloaders like TWRP or CWM made for the A100?
- aswell ZeroNull's unlock bootloader method?
- which custom ROM's do support 3G? I'm thinking about pio_masaki's Jellytime Sosei, his CM10 build, or KEBBERSROM...(?)
rather an ubuntu related question:
Am i fine with installing the packages: android-tools-adb & android-tools-fastboot or do i need the full - Android-SDK?
The most important thing for me is to get rid of acers bloadware, so i'm planning to install TWRP followed by a nandroid backup and kiling them softly *fingerscrossed*
running StockRom: Acer_AV0141_A101_1.015.00EMEA_DE
Click to expand...
Click to collapse
Cwm and twrp are recoveries, not boot loaders, and are fine for the 101, no worries there. Everything for the a100 works for the 101 except the Roms, a100 ROMs on a101 kills 3g. You lose 3g, period. Cm10.1 I had some experimental 3g stuff in there but I never heard back on that.
Maybe I'll see about adding it to cm10.
Sent from my HTC DNA
pio_masaki said:
Cwm and twrp are recoveries, not boot loaders, and are fine for the 101, no worries there. Everything for the a100 works for the 101 except the Roms, a100 ROMs on a101 kills 3g. You lose 3g, period. Cm10.1 I had some experimental 3g stuff in there but I never heard back on that.
Maybe I'll see about adding it to cm10.
Sent from my HTC DNA
Click to expand...
Click to collapse
Thats too bad to hear but i was expecting this. Just thaught that CM10 could have 3G functionality since some friends are using cyanogen on their phones. And since Sosei lacks of GPS it's not an alternative for me either. After all i convinced my wife to buy the a101, so that we can use it as navigation aswell ;P
well well, i really would appreciate the 3G Feature in your CM10, but i dont wanne hassle so - just if you have time for it of cause.
greetings and thanks so far
VolkerPfosten said:
Thats too bad to hear but i was expecting this. Just thaught that CM10 could have 3G functionality since some friends are using cyanogen on their phones. And since Sosei lacks of GPS it's not an alternative for me either. After all i convinced my wife to buy the a101, so that we can use it as navigation aswell ;P
well well, i really would appreciate the 3G Feature in your CM10, but i dont wanne hassle so - just if you have time for it of cause.
greetings and thanks so far
Click to expand...
Click to collapse
It can have 3g just fine, I've asked a few times for the 3g ril files from 101 users wanting me to build for them, they always vanish and I never hear back about it.
A100 just had its rotation for builds last night / this morning so it'll come up again sometime between wed-fri I think. Been looking at updating the black bean build and maybe adding AOKP as well, I'll use them for testbeds. I may go ahead and just do an extra day on the A100 and see about getting a potential 3g build up for you.
Side note, sosei will use gps if you use the newer cm10 boot.img.
Current rotation is:
Nexus 7 holds priority as I've been invited to Team Sorcery as their N7 dev.
Toshiba Thrive 4.2 development, 4.1.2 updates and kernel work (voodoo sound) comes second as they've been extremely generous to me.
Droid DNA aosp porting as the device was pretty much donated
Slight GNex work as needed, rare
A100 is bottom/last as I don't own one, luckily fixes from the thrive usually directly move over to the A100
Other devices I don't own.
I have a few things planned for the A100 for some nice updates and releases to jeep you guys in a variety of ROMs, like AOKP and some updates to the cm9 kernel I use.
Sent from my Nexus 7 - JBSourcery 4.5
pio_masaki said:
It can have 3g just fine, I've asked a few times for the 3g ril files from 101 users wanting me to build for them, they always vanish and I never hear back about it.
A100 just had its rotation for builds last night / this morning so it'll come up again sometime between wed-fri I think. Been looking at updating the black bean build and maybe adding AOKP as well, I'll use them for testbeds. I may go ahead and just do an extra day on the A100 and see about getting a potential 3g build up for you.
Side note, sosei will use gps if you use the newer cm10 boot.img.
Current rotation is:
Nexus 7 holds priority as I've been invited to Team Sorcery as their N7 dev.
Toshiba Thrive 4.2 development, 4.1.2 updates and kernel work (voodoo sound) comes second as they've been extremely generous to me.
Droid DNA aosp porting as the device was pretty much donated
Slight GNex work as needed, rare
A100 is bottom/last as I don't own one, luckily fixes from the thrive usually directly move over to the A100
Other devices I don't own.
I have a few things planned for the A100 for some nice updates and releases to jeep you guys in a variety of ROMs, like AOKP and some updates to the cm9 kernel I use.
Sent from my Nexus 7 - JBSourcery 4.5
Click to expand...
Click to collapse
thats of cause comprehensible, since these iconias are quite old, right. And if i didnt needed the (3g)/hdmi (looking forward for ubuntu for android) i guess i would have baught an Nexus 7 aswell. However, in two weeks i got an exam and i'm investing way too much time right now in reading about all that stuff here so if you could direct me were to read about this 3g ril files or tell me how i can find them on the mashine i'll send it to you. I've read something about the build.prob but no mentions about 3g, cellular or ril or whatsoever in it. Also a "find" gave me nothing.
Unfortunately i have to read some annoying §&"/%§ now but i've set up the email notification now.
greetings
Related
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€
I have been looking for a couple of weeks, but I can't find anything that is just this. I don't know much about development, so I wouldn't know how to take what someone else has done and modify it to how I want.
Basically, I am wanting a Paranoid Android soft key area. I want to get rid of the nav bar up top and move my clock, battery, signal, wifi, etc. to the bottom with the soft keys. That is the only change I really want to make.
I know that this is one of the premier features of Paranoid Android, but it is my understanding that PA for JB is based on CM10 and still has a lot of bugs to flesh out, especially on the CDMA/Toro version. Also, I do not know enough to figure out the tablet mode, hybrid mode, and regular mode stuff, especially since some of it is done in ADB (again, my understanding of it, I could be wrong).
Is it possible to do only what I described without flashing to PA for JB? I feel like some of the modifications I have seen posted in this forum come close to this, but the ones I remember off the top of my head move only the clock to the bottom.
Thanks to anyone who can help.
May I ask, why you dont want to flash PA? what bugs are keeping you from flashing?
I am currently running it and there are no real bugs, that irritate me (I dont use bluetooth^^)
And since a new build will be coming very soon even the toro devices should be fine aswell.
Nordpolcamper said:
May I ask, why you dont want to flash PA? what bugs are keeping you from flashing?
I am currently running it and there are no real bugs, that irritate me (I dont use bluetooth^^)
And since a new build will be coming very soon even the toro devices should be fine aswell.
Click to expand...
Click to collapse
I will definitely flash PA in the future, I would just prefer to wait until all the bugs are kicked.
First, I need to be able to be reached on my phone all day and by email (which I check 95% of on my phone) at all times. Apparently there is a problem with gmail on PA right now, as well as other smaller bugs. While I can't name any specifically that I remember, I do know the developer himself is calling it very alpha. While I love the developer-made ROMs, I also need stability, at least until the summer is over and I'm back in school.
Second, it is my understanding (I love that saying, obviously) that you have to do a full wipe each time you flash a new version of any CM-based ROM. Because I hate having to re-download and re-log into all of my apps (especially ones that need credit card numbers), I usually stay on stable ROMs that allow me to dirty flash when newer versions are released. I know there are ways around this, but I don't know enough to get around it at the moment nor do I have time to learn how to do it until school starts back up.
TexPP said:
I will definitely flash PA in the future, I would just prefer to wait until all the bugs are kicked.
First, I need to be able to be reached on my phone all day and by email (which I check 95% of on my phone) at all times. Apparently there is a problem with gmail on PA right now, as well as other smaller bugs. While I can't name any specifically that I remember, I do know the developer himself is calling it very alpha. While I love the developer-made ROMs, I also need stability, at least until the summer is over and I'm back in school.
Second, it is my understanding (I love that saying, obviously) that you have to do a full wipe each time you flash a new version of any CM-based ROM. Because I hate having to re-download and re-log into all of my apps (especially ones that need credit card numbers), I usually stay on stable ROMs that allow me to dirty flash when newer versions are released. I know there are ways around this, but I don't know enough to get around it at the moment nor do I have time to learn how to do it until school starts back up.
Click to expand...
Click to collapse
well that gmail issue is a myth^^ you can simply change the dpi to phone and everything works flawless
Furthermore moles said, that form 1.7 onwards you wont need a factory reset anymore^^
Nordpolcamper said:
well that gmail issue is a myth^^ you can simply change the dpi to phone and everything works flawless
Furthermore moles said, that form 1.7 onwards you wont need a factory reset anymore^^
Click to expand...
Click to collapse
Thanks for the info. I just sent you a PM regarding some of what I said, but I sent it before seeing this reply. I may try to jump on PA tonight if it is working better.
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.
does anyone know, or have a reason, or encounted in a problem with CM 10.1 cuz i recently installed CM 10.1 stable on my ATT S3 and it keeps restarting itself after 20/30 minutes tops, maybe longer but once in a while it randomly restarts itself
installed everything perfectly, no reason to be acting crazy since its from CYANOGENMOD TEAM but ROMS are not perfect or as good as STOCK ROMS (that come pre-installed on your device)
any issues, bugs, any kind of thing you have noticed with cm 10.1 yu can post it here
new upcoming features, fixes, what should be there or shouldnt be there, whats missing everything
HELPING EACH OTHER SOLVE SIMPLE/SERIOUS with CM 10.1 and above ISSUES
am currently running Synergy ROM 4.1.2 Stock rom with ZIGGY KERNEL (clocked at 1.3 Ghz) and its pretty sweet, stable, good battery, perfomance is top notch for a stock based rom that come with all samsung boatload
SO DUMP ALL THE PROBLEMS/SOLUTIONS IN THIS NEW THREAD FOR CM 10.1 AND ABOVE - ATT S3 I747
ANYTHING YU THINK IS COOL/AWSOME ABUT CM 10.1 ON YOUR AWSOME S3 GET IT HERE
Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE
winosxbuntu said:
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE
Click to expand...
Click to collapse
First and foremost, no OS or software, including android, is perfect. Secondly starting a new thread does not mean it will not get "cluttered" either. The ROM thread for CM is not as bad as you make it out to be. The idea is that the newest material covers the most recent nightlies. It is not that difficult to go to the end and work backwards. In regards to you random reboots, look on JIRA as it exists for this very reason. Take a logcat and report on JIRA if not already covered. JIRA gives you all the bugs reported and their current status towards a fix. This is a wasted thread for this very reason.
As far as ROMs being different...that is the point. Each developer(s) put their own spin on it. That is what makes these development threads so great. You can look for a ROM that you like best. Some ROMs are more universal (but you still need your device specific version), such as CM, while others are device specific.
And phones are not created equal. They may look the same, have the same hardware specs, and all else seemingly equal, but slight manufacturing imperfections make them different. Two people can have the exact same phone from the same carrier, manufactured on the same day, but due to some ever so slight differences from imperfections, ROMs will work differently on each. For instance, in your case CM reboots randomly. For others, such as myself, this is no longer an issue. However, it is possible that another ROM will work great on your phone but not on mine.
While you say CM is not perfect like the stock rom, the stock rom is not perfect either. I have AT&T and the stock rom has several issues. The lockscreen securities can be bypassed, the alarm likes to not work at random times (software bug), and every now and then I get a battery plummet after a phone call when the phone switches between 4G and 4G LTE. Others may or may not have these issues but they seem to be rather common (the security bypass affects all S3 phones that were on 4.1.1 that I am aware of). For this reason I stick to custom roms because I do not have these problems which I personally view as severe for me (Aside from protecting my data and enjoying battery life, I rely on my phone as an alarm clock). Now that 4.2.2 has come as far as it has, it is stable enough that I can use it as a daily driver. I knowingly accept any bugs that are there because typically the ones that exist do not have a large affect on me, if at all, unlike the stock rom.
Greetings, everyone!
I've been having issues with my Captivate Glide lately (related to the battery going bad... again) and with the recent money I spent ordering a new replacement battery and also an extended one, I want to give my phone a new lease on life since there are no real contenders in the QWERTY realm for Android. I have a few questions, which are probably all foolish and simple, but I'm reading about all the things you can do to these phones and it's all going over my head so far, I'm not picking up on ANYTHING from these threads. Hopefully somebody can ELI5 and help me out.
1) Stock is Android 4.0.4 from what I understand. I found the "EVERYTHING SAMSUNG SGH-I927" thread and there are 4.2.2 and 4.3 ROMs. But they come with issues. Not something I really want to mess with? But what am I missing out on from 4.2.2 VS 4.3? And what do I really gain from 4.0.4 to 4.2.2?
2) There was another thread mentioning spyke555's CM10.1 4.2.2 ROM and I looked at the thread here (http://forum.xda-developers.com/showthread.php?t=2217288) but hasn't been updated in several months. The last post in the thread had this suggested for different ROMs but I have no idea how to tell the differences or make a choice between them. What should I be looking for?
PAC-ROM (JB 4.3)
http://goo.gl/uG4LFM
My favorite as of yet. A combination of CM, AOKP, and PA, this rom has it all!
CM 10.2 (JB 4.3)
http://goo.gl/Yklv9E
A good one, my second favorite because of the functionality. Same issues with any other CM.
LiteRom (ICS)
http://goo.gl/CNsmM7
Haven't used this one yet, but if you like ICS and a snappy phone, this seems about right.
LiquidSmooth (JB 4.1.2)
http://goo.gl/Ic5dgL
My third favorite, used this one for months! Fast, functional, and nice looking!
BONUS:
TWRP TOUCH FOR CAPTIVATE GLIDE:
http://goo.gl/1dSjzU
Probably the best recovery I've used for the Cappy Glide. Very nice, and is touch screen!
3) What is the difference between kernel / ROM / etc? I'm getting the impression that the kernel is more of a BIOS for the phone, and ROM's are the OS? Am I on the right track here? I've seen people say kernel affects the battery life and base performance more though, so the kernel also has some OS functionality in the hardware department?
I'm not a power-user by any means, but I just want to wake up my phone a little bit and get rid of the AT&T bloatware that is all over the phone. Going back to a stock Android theme doesn't bother me at all since I am neutral on TouchWiz anyways. I just started looking up different things for my phone and immediately got lost. Thank you for taking the time to read my super-long first thread!
EDIT: This was spurred due to my phone continually re-starting at random points throughout the day, which I thought was the battery, but now I believe it was a corrupted file for Android. I flashed TWRP but I don't have a way to get a custom ROM onto my MicroSD card. Is there a way through Odin or some other program that I can push a custom ROM to my phone while hooked to the computer?
Vexarana said:
1. But what am I missing out on from 4.2.2 VS 4.3? And what do I really gain from 4.0.4 to 4.2.2?
2. There was another thread mentioning spyke555's CM10.1 4.2.2 ROM and I looked at the thread here (http://forum.xda-developers.com/showthread.php?t=2217288) but hasn't been updated in several months. The last post in the thread had this suggested for different ROMs but I have no idea how to tell the differences or make a choice between them. What should I be looking for?
3. What is the difference between kernel / ROM / etc? I'm getting the impression that the kernel is more of a BIOS for the phone, and ROM's are the OS? Am I on the right track here? I've seen people say kernel affects the battery life and base performance more though, so the kernel also has some OS functionality in the hardware department?
4. I'm not a power-user by any means, but I just want to wake up my phone a little bit and get rid of the AT&T bloatware that is all over the phone.
5. Is there a way through Odin or some other program that I can push a custom ROM to my phone while hooked to the computer?
Click to expand...
Click to collapse
1. 4.3 has bugs not found in 4.2.x but in my opinion doesn't bring new mentionable features around. Interface does change a little and some additional settings like tweaking button backlight is added. I see these latest CM builds as a showcase of what our device is capable of, i.e. if we can run a CM10.2 then we can potentially run all kinds of Android 4.3-based ROMs. All non-stock ROMs (CM, Liquid, PAC) completely gets rid of AT&T bloats (phone runs much faster and with more free RAM) and try to bring in more customization, like CM's cLock and PAC's HybridProperties. In this case the 4th question is answered: a custom ROM would be the shortest cut to a bloat-free experience.
2. I don't think there's a need for an update to CM10.1 (latest is 10.1.2), because it's really stable apart from those bugs that exists across all non-TouchWiz ROMs. I'm using this as well (this post is sent from my Glide with CM10.1.2). If you want drastic changes in the interface, look at PAC, but prepare to sacrifice stability. And if you strive for more speed, Liquid should be okay (lower Android version usually means faster).
3. Await others' more exact answers (I usually don't use custom kernels), though kernel provides driver for all hardware and determines CPU/GPU frequency, governor, etc., so performance and battery life are all tied to it.
5.You have TWRP - superb! If you haven't set up ADB first, do it. Then in TWRP, go to Advanced-ADB Sideload, swipe to continue and connect Glide to PC. from PC, open a command prompt window and type "adb sideload **path to your ROM zip on PC**".
Good patience if you've gone through all my opinions
Sent from Samsung Captivate Glide @ CM10.1.2
AndyYan said:
5.You have TWRP - superb! If you haven't set up ADB first, do it. Then in TWRP, go to Advanced-ADB Sideload, swipe to continue and connect Glide to PC. from PC, open a command prompt window and type "adb sideload **path to your ROM zip on PC**".
Click to expand...
Click to collapse
I tracked you fully all the way up to ADB. What is an ADB? How do I set one up? I tried to search but it said it was temporarily down
EDIT: Okay so I ended up just getting a $10 microSD to USB adapter at the BX. AND IT WORKS! IT BOOTED!
EDIT2 (but not really I did it at the same time): So... it boots. And it works. And it's beautiful and snappy and gets texts and calls (which is important since I'm military) but my power button doesn't work. Do I need to set it up somehow in the settings? It also did this in the booter. Before I put TWRP on, using the stock booter, it wouldn't let me select anything with the power button. Volume rockers worked fine though. But when I boot, and hold power and volume down, it opens up the booter fine! I'm just excited to have a phone at this point and could care less. I used spyke555's ROM for now just to get it working.
EDIT3: Going through using the phone. Power button still does not register. Volume rockers also do not wake phone but work when phone is already awake. I just slide keyboard open and closed each time to wake it up. Tried to send a photo through MMS and the phone re-booted though. I'm not sure if the battery was the issue after all? Will report back after going to the mall and playing with it a bit more.
You might have a bad power key after all
Sent from Samsung Captivate Glide @ CM10.1.2