Related
Have got the version of flash that's in the CWM sticky, but noticed my N1 today got an upgrade, and am wondering if there is a way to pull that over to my G-tab? Or do I just need to be a little patent and someone will post an update in a day or two?
EwanG said:
Have got the version of flash that's in the CWM sticky, but noticed my N1 today got an upgrade, and am wondering if there is a way to pull that over to my G-tab? Or do I just need to be a little patent and someone will post an update in a day or two?
Click to expand...
Click to collapse
You can try but the flash seems to be device specific in some cases so it may just bork your flash. Make a backup so you can restore it if you try
EwanG said:
Have got the version of flash that's in the CWM sticky, but noticed my N1 today got an upgrade, and am wondering if there is a way to pull that over to my G-tab? Or do I just need to be a little patent and someone will post an update in a day or two?
Click to expand...
Click to collapse
Since you mention CWM I will assume you have root.
Get a free Dropbox account and install on your N1 and gTab. Then it's as easy as copying the Flash apk into the Dropbox folder on your phone and then downloading it from your Dropbox folder on your gTab.
Doesn't get much easier.
I saw the flash update on my N1 this morning. I read the release notes for 10.1.106.16. It states:
Flash Player (10.1.106.16) impacts new users only and is not a mandatory update for existing users. It SHOULD NOT be installed on devices/tablets with the NVIDIA Terga 2 Super Chip including the LG Optimus 2X, Dell Streak 7, and Motorola ATRIX. The pre-installed version of Flash Player is optimized for Tegra 2 (this is my addition... if only there was a pre-installed version of the Flash Player installed on the gtab...) Future updates will include these optimizations. If you are unsure as to whether your device includes the NVIDIA Tegra 2, please consult your device owner's manual.
Maybe the versions prior have the same stipulation I don't know (this is the first time I saw this), but it's probably best to stick with what works for now. Probably won't be a lot of change until the release with the official Tegra 2 support is made available.
sjmoreno said:
Since you mention CWM I will assume you have root.
Get a free Dropbox account and install on your N1 and gTab. Then it's as easy as copying the Flash apk into the Dropbox folder on your phone and then downloading it from your Dropbox folder on your gTab.
Doesn't get much easier.
Click to expand...
Click to collapse
The update says in it's notes that it isn't for tegra devices... kinda useless to us.
6/5/2011 EDIT : Going to alter this post for two reasons. First, the information inside is pretty old news and stale for most, and not even very relevant for new users. Second, there is STILL confusion between these two branches that needs to be ironed out, imo.
6/20/2011 EDIT: Added some links to the assorted mods (and google searches for anything not on XDA, to abide by the rules). Also, goodintentions has a new site up that is VERY helpful for new user questions. It is here: http://viewsonic-gtablet-for-dummies.webs.com (I assume this link is OK to advertise, as it hasn't been pulled by the moderators yet).
If you are considering modding your new GTAB, I would suggest reading this. It's going to be a long read, but you'd rather not brick your device, right?
Some Terminology Pre-Reqs to Understand
"Soft-brick". The device is not booting up properly anymore, but is potentially fixable by using a tool called "nvflash".
"APX Mode". The is a low-level mode on the GTablet where you can makes repairs and un-brick the device.
"Nvflash". This is the name of the actual tool you use, when you are in APX mode.
"Clockworkmod". This is an alternate recovery tool. It adds a few things that the 1.1-based stock recovery does not have, such as full image backups, wiping user data and SD repartitioning. The 1.2-based stock recovery is a little better, but clockworkmod still has more options than 1.2 standard recovery
"/data partition". This is the area on the device where all your user data and user apps reside. A factory reset will wipe this area.
"/sdcard partition". This is the area on the device where all your content resides. It's also the area that gets mounted on your PC.
"Data wipe" or "User data wipe". This is a factory reset -- all user apps and data will be erased. Content in the device's /sdcard is not touched.
"SD repartition". This is a data wipe and a wipe of /sdcard. So both areas are erased.
"ROM" as defined for use should be considered a BOOT ROM. This is the base program running on your tablet, like an operating system it is the first line of code to load and while not every rom is a full replacement of the viewsonic operating system only one can be loaded at a time. (thanks mERRIL!)
"Kernel" as used here is the tablets details and settings written out so the software knows how to interact with the hardware. This is where things like overclocking can be done, along with changing the way your backlight or wifi utilizes power. (thanks mERRIL for both of these!)
Two Development Branches, and How to Check which version you have
This is the FIRST thing any new Gtablet user should check imo, before you attempt to mod your device. Viewsonic / US Merchants released a new development branch with a new bootloader and kernel (which they later pulled), and older mods do NOT play nice with it. There have been reports that at least a few TigerDirect users have gotten 4349 OOTB.
So, to check which branch you are on if you are on STOCK: Go to Settings -- About Tablet -- Tapu UI Version. If your firmware starts with "1.1", then you are on the 1.1 (old) branch. If your firmware starts with "1.2", then you are on the 1.2 (new) branch. Also an obvious difference between the two is that the 1.2 branch adds a lockscreen to the tablet.
The "Two Cliffs" analogy
Try to think of these two branches as two cliffs. If you are on either side and want to mod your device, the safest way is to use a mod that is built around the branch you are on. Here on XDA Developers site, most of their mods and custom kernels are based on the 1.1 branch (as of this writing 6/14/11 EDIT: That seems to be changing). For 1.2 based mods, there are several options but most of them are not posted here on XDA. So you have options regardless of which branch you are on. There is no advantage of using one over the other, except possibly vendor support - 1.1 is still the ROM offered by the vendor, given that their one released 1.2 ROM was pulled.
It is possible to jump from 1.1 to 1.2, and back again. But think of this as a bridge between the two. I have done extensive tests in the last month on this, and it does work MOST of the time if you follow directions. But even when doing everything right , there is still a small chance that you will "fall of the bridge" and into the abyss (soft-brick). And if you attempt to jump between them with clockworkmod, you will fall for sure, 100% of the time. Think of clockworkmod as a "bridge that is out".
The most sturdy bridge, going on my own testing, is the one based on build 1.1-3588 full stock. This makes sense because this is what Viewsonic would want you to be on, before jumping to 1.2. The reverse (1.2-4349 stock, for example) is also fairly sturdy. But again, it is a higher risk than staying within the same branch.
I'm on a 1.2-based stock ROM. What are my modding options?
If you are on the 1.2 branch, there are actually quite a few options right now. The challange for a user is finding them and understanding that you have to be careful if you try to use a 1.1 mod instead (see the "Two Cliffs Analogy", above).
The current 1.2 based options on XDA (as of 6/16/11) are:
- Calkulin+Clemsyn 1.5ghz Froyo Combo VERSION 6
- Beasty's 2.2.1 ROM (Adam) + Clemsyn ver 11 1.5ghz kernel
- Clem / roebeet Honeycomb alpha combo (this is a Clem creation and is actually forked from my own HC port)
- Honeycomb Android Illuminate for The Gtablet
- Gingerbread Rom Collection for Bootloader 1.2 (these are CM7 ROMs ported to the 1.2 bootloader)
The current 1.2 based options NOT hosted on XDA (as of 6/16/11) are:
- Honeycomb for GTAB - Flashback
- Century Eyes (Froyo based "EDEN" port)
- Mountain Laurel (Froyo based "TapnTap" port)
- Brilliant Corners (Froyo based "VEGA"/"Viewpad" port)
- Bottle of Smoke Honeycomb port
Pershoot and Clem both have 1.2 kernels that you can use, as of this writing. Not all of that information is here, some are on other sites.
I'm on a 1.1-based stock ROM. What are my modding options?
On XDA, there are still a number of mod options and customized kernels, at your disposal. Again, a 1.1 to 1.1 mod should be fairly safe to attempt. If you need to jump to 1.1 from 1.2, I would recommend reading the modder's post to see if there are instructions for 1.2 jumpers.
The current 1.1 based options on XDA (as of 6/16/11) are:
- VEGAn-Tab Froyo Build
- ZPad Clean v3.0 for gTablet
- VEGAn-TAB GingerEdition
- G-Harmony Gingerbread 2.3.4 with Honeycomb elements
- Calkulin's G-Tab [ 3991 l Battery Saver script w/ Profiles ]
- Evervolv | GRJ22/Android 2.3.4
- Gingerbread-gtab-deck
- GtabComb for Bootloader 1.1 Gtablet\Zpad T (this is a zyhong creation and is actually forked from my own HC port)
- TNT Lite Froyo (similar to Calkulin's ROM, and currently retired)
- gADAM Froyo (currently retired, as well)
The current 1.1 based options NOT hosted on XDA (as of 6/16/11) are:
- Cyanogenmod 7.x
There are also a few custom kernels for 1.1, specifically the ones by Pershoot and Clemsyn, here at XDA.
OK, so I've confirmed that I'm on one dev branch but I want to use a mod that's on another dev branch - what do I do?
My suggestions:
1- Read the modder's first post, for possible instructions.
2- If there are no instructions for branch jumpers, DO NOT assume that it's safe to jump. Ask the modder first, to be sure.
I am generalizing here, but the older 1.1 mods might not have instructions for 1.2 users, as 1.2 didn't exist at the time the mod was created. Imo, the SAFEST way to jump to a mod that's on another branch is to use stock. So 3588 stock to 4349 stock (using standard recovery) to go up, and 4349 stock to 3588 stock (using standard recovery) to go down. The main reason why it's the safest is because stock has the bootloader image in there, which is required to jump.
Also, gojimi has a post with instructions for 1.2 to 1.1 downleveling: http://forum.xda-developers.com/showthread.php?t=1036956
I attempted a 1.1 to 1.2 (or vice versa) jump, and now I'm stuck at the birds. Is this a soft-brick?
Yes, it's a soft-brick if you are stuck at the birds. You'll need nvflash the device to fix it. There is information here on XDA on how to do that, or you can find this on other tablet sites.
I attempted a 1.1 to 1.2 (or vice versa) jump, and now I'm stuck at the GTablet screen, or I'm boot looping. Is this a soft-brick?
Probably not - more likely is that you just need to do a data wipe, or a SD repartition if that does not work.
I have a Hannspad (or an Olipad) - does this apply to me?
I believe that it does, going on what I've read. Both these devices seem to be based on the TapUI, and the 1.2 development branch. So attempting a 1.1 GTAB ROM will likely have the same pitfalls. Also keep in mind that even 1.2-based GTAB ROMs have issues. for example, the Hannspad can boot a 1.2-based ROM (like "Bottle of Smoke") but the side keys won't work because the hardware is different. I don't have these devices myself, but I am going on third-party information.
Roebeet, can I safely install over the 3588 Stock Enhancement and Market Fix? I hate to lose the Market but definitely don't want to deal with a brick right now. Another user indicated he/she installed the update over a similarly configured machine and it worked but then applied the Stock Enhancement and Market fix and soft bricked.
I appreciate all the work you do for other users, including me.
interesting!!!
I love my devs!!! Seriously you guys rock!!!
P.S. I am sticking with Vegan GingerEdition
Great post and good info roebeet - stickied for the immediate future.
MSU_Sparty said:
Roebeet, can I safely install over the 3588 Stock Enhancement and Market Fix? I hate to lose the Market but definitely don't want to deal with a brick right now. Another user indicated he/she installed the update over a similarly configured machine and it worked but then applied the Stock Enhancement and Market fix and soft bricked.
I appreciate all the work you do for other users, including me.
Click to expand...
Click to collapse
I haven't tested all scenarios, as there are just too many of them. I specifically picked VEGAn as I know that's a very popular ROM and I could see new stock users flashing to that.
Rule of thumb: If you are going from a 1.1-based ROM to a 1.2-based ROM (or vice versa) and use clockworkmod, you will soft-brick your device.
Great work! More coffee for Roebeet
I guess ... better stick to TNT Lite 4.4 for now.
I am curious about (not in any hurry tho)
cwm+TnT Lite 4.4 ->fixrecovery.sh -> stock 3588 ->OTA 4349
--
msu_sparty.
I ran 3991 for a good while during the time the Wooters needed help.
I tried to install the Enhancement Pack on 3991 and it semi-bricked my
G-Tablet.
I wouldn't try it until someone tests it for sure -- unless you want to
be the tester!!!???
Rev
cbay said:
Great work! More coffee for Roebeet
I guess ... better stick to TNT Lite 4.4 for now.
I am curious about (not in any hurry tho)
cwm+TnT Lite 4.4 ->fixrecovery.sh -> stock 3588 ->OTA 4349
--
Click to expand...
Click to collapse
cwm+TnT Lite 4.4 ->fixrecovery.sh -> OTA 4349. This might work. Haven't tested it yet, but I will. It worked for build 3991, so it might work with 4349.
EDIT: One test, one success. Again, YMMV.
As a new tab owner where do I find the build number please?
Thank you
roebeet said:
cwm+TnT Lite 4.4 ->fixrecovery.sh -> OTA 4349. This might work. Haven't tested it yet, but I will. It worked for build 3991, so it might work with 4349.
Click to expand...
Click to collapse
Does fixrecovery.sh also add/enable the OTA updater? Or is there a update.zip for 4349 somewhere?
thanks for all the work,
--
Can 3588 enhancement be loaded with gapps for android market?
SoCal2 said:
As a new tab owner where do I find the build number please?
Thank you
Click to expand...
Click to collapse
Just go to settings-about device
butchconner said:
msu_sparty.
I ran 3991 for a good while during the time the Wooters needed help.
I tried to install the Enhancement Pack on 3991 and it semi-bricked my
G-Tablet.
I wouldn't try it until someone tests it for sure -- unless you want to
be the tester!!!???
Rev
Click to expand...
Click to collapse
Can you point me in the right direction to unbrick this thing? It semi-bricked mine, and I don't know where to start.
SoCal2 said:
As a new tab owner where do I find the build number please?
Thank you
Click to expand...
Click to collapse
Settings about
Thank god I was impatient and installed vegan 5.1.1 before this happened! Was waiting for ota 3588 before root as I was on 3389 this morning. I'm sure you guys won't be long figuring out if there anything worthwhile here.
cbay said:
Does fixrecovery.sh also add/enable the OTA updater? Or is there a update.zip for 4349 somewhere?
thanks for all the work,
--
Click to expand...
Click to collapse
No, it does not. All it does is flashes back 3588 recovery which is the recovery needed to flash between a 1.1-based and 1.2-based ROM.
yay! what we all knew to be the case a month ago is finally confirmed.
SoCal2,
The version number etc. is at Setting/About.
Rev
just lou,
A good start would be to read this thread. If you can do this procedure, it will NVFlash you back to stock version 2638 -- which we call bekit 1105 a lot.
http://forum.xda-developers.com/showthread.php?t=861950
Once you get to 2638, you can set up wifi and it will fairly quickly bring you an OTA Update notice and you can move up to 3588 -- and you can go where you want
from there.
Rev
Well best I recall mine was running 3588--whatever upgraded when I got it a couple weeks ago.
Sae the upgrade a few minutes ago, and opted to load it.
Now sits at "home", shows current (working) time, that I have linksys, that it is charged ((86%) and that sound is on.
Nothing else works. Oh yes, there is lower right hand icon showing an open padlock.
This came up after upgrade. I've powered off and on a couple of times.
Any recommendations?
Hello,
I have a HTC Touch Diamond 100 and I installed the "Froyo FRX06 XDandroid NEW system update" review in the post "[prj] [XDANDROID] [AOSP] [FroYo | GINGERBREAD] [31.03] System Update" and everything works fine except that it doesn't recognize SDcard applications.
There's no Error Message in the screen, is just that the system doesn't recognice anything in the SDcard. I put my apps in the folder: AndroidApps-> Other. I think it's not the common fault that I have read many people have "Waiting for SDCard error. For people who have problems with sdcard message, add this to your startupmsmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave" because for instance the phone let me save the pictures i've take with the camera phone or install and recognice any app from the market.
I 've Format the card with the HP tools after initial installation and then i had restore all the files in the internal storage.
P.S. Sorry for my possible spelling mistakes but English is not my native language
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
R^7Z said:
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
Click to expand...
Click to collapse
Oh what A noob mistake xD I didn't know that apps in the "Other" folder doesn't follow the "typical rules" for instaling apps (i've come from previous releases of Android, Eclair specifically, and in that version it was only place in this folder to install apps).
I'm using froyo instead of gingerbread builts because HTC touch Diamond it's quite old and i don't know if the performance would be better or slower than froyo performace but if you recomend me to use that gingerbread bundle i would use it.
Thanks R^7Z.
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
R^7Z said:
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
Click to expand...
Click to collapse
I see what you say but honestly, right now, I'm looking for stability and performace, if you know that gingerbread build GBX0A have better performance (i supose that it's less stable because it's an alpha) than FRX06 i'll choose Ginger
Thanks again R^7Z.
This is my first attempt at a custom ROM for any Android device, so bear with me. I did not build this from AOSP source, or any other source code. It's entirely from ASUS. This ROM is intended for those who don't like the stock ASUS apps, similar to KRAKD/FROZN, except I've not optimised any of the APKs or anything else. Hopefully this can be a useful base ROM for another dev, taking the tedious part out of the equation. It's completely based on US, not WW or TW.
It's large(300Mbyte) because I used a binary blob. I'm working on shrinking it down with a proper update sript.
Apps I removed:
Amazon Kindle
MyCloud
ASUS File Manager
MyLibrary
MyNet
Netflix
News & Weather(and their widgets)
PolarisOffice
PressReader
MyZine
Tegra Game Zone
Web Storage
Zinio
PC Sync
ASUS Software keyboard(the touchscreen one, not the dock keyboard)
DMClient(related to ASUS updates, from what I understand)
ASUS software update(so no annoying OTA notifications that you can't use anyway)
SuperNote
-any others not included that I forgot to list
How to install:
1. A complete data wipe(at least dalvik & cache, data is optional) is strongly recommended if you're coming from Honeycomb.
2. Flash the zip from CWM.
3. Enjoy your new ICS.
You should be able to flash from any ROM if you clear at least dalvik and cache.
Features:
-Pre-rooted for your convenience, with busybox, su, and SuperUser.
-ALL bloatware removed, hopefully improving performance
-Closer to an AOSP experience due to all bloat being removed.
What this ROM does NOT have:
-Custom kernel
-Stock ICS buttons(it has the crummy ASUS back, home, recent app buttons)
-Zipaligned APKs
-Deodexed APKs
-A name, since it doesn't really need one right now.
How I created it(roughly, not a step by step):
1. I reverted from a custom ROM(krakd) to the latest US .21 HC release, with stock recovery
2. I Rooted with nachoroot and then used OTA keeper to unroot
3. I updated to US ICS via OTA.
4. I reapplied root with OTA keeper
5. I used ES file manager and terminal to remove the apps
6. I used ES file manager to add SuperUser to /system
7. Installed busybox at some point during these steps, I forget when.
8. Used dd to image the /system partition(mmcblkp0) to a file on my MicroSD
9. Replaced the LNX and APP blobs of a Honeycomb update(.21) with the ICS ones
10. Flashed it, and it worked.
So it's not a "proper" update, broken down into directories and such, but it does work.
Links:
ROM: http://dev-downloads.com/asus-tf101-romwipicsus-9-2-1-11-4-0-3-minimal/
Trebuchet CM9 launcher: http://dl.dropbox.com/u/31118/signed_TrebuchetCWM.zip (thanks to whitekidney/wk on #asus-transformer irc)
Here is the MD5 for the ROM zip: 0B9BC1C83C271DF26501CF533A046CB1
And the SHA1: B7BBC2C3AB33844E46CC8D8D2900E2AF1C68EFB5
Credits:
Whitekidney for the Trebuchet launcher upload
Have you tested this at all?>
Yes, why? It worked fine on my TF101.
I think everyone is always a bit skeptical of a ROM that someone says openly is their first attempt and they have less than 10 posts on here..you are after all talking about potentially rendering a $500 device useless..people are usually right to exercise caution..when the developer cannot post in the dev section because his post count is too low!
But hey, that is how Paul Burton started here, though it was not his first ROM I am quite positive..
daxtsu said:
Yes, why? It worked fine on my TF101.
Click to expand...
Click to collapse
After flashing, not booting anymore, and as I I know what I am doing...unless my power cord just broke.
thanks I guess, but I can remove my own apps From a rom ......
luna_c666 said:
I think everyone is always a bit skeptical of a ROM that someone says openly is their first attempt and they have less than 10 posts on here..you are after all talking about potentially rendering a $500 device useless..people are usually right to exercise caution..when the developer cannot post in the dev section because his post count is too low!
But hey, that is how Paul Burton started here, though it was not his first ROM I am quite positive..
Click to expand...
Click to collapse
Fair enough, I do admit I'm new to Android development, but I wouldn't release something without testing it on my own device first.
DTgreat said:
After flashing, not booting anymore, and as I I know what I am doing...unless my power cord just broke.
Click to expand...
Click to collapse
Did you do a full wipe? I installed it at least 5 times today during testing removing apps with no major issues..
BTW: Here is the MD5 for the zip: 0B9BC1C83C271DF26501CF533A046CB1
And the SHA1: B7BBC2C3AB33844E46CC8D8D2900E2AF1C68EFB5
Yes, although like I said. I know what I am doing. My power cord in fact, may have just broke. (Although I doubt it.)
IF YOU cant post links yet it's for a reason
cool, where did you get the source code from asus?
timbit123 said:
cool, where did you get the source code from asus?
Click to expand...
Click to collapse
It sounds like he got the ROM and removed the third party apps, not that he got the source code to build it to AOSP.
its more a list of apps that are safe to remove with TB...... IMO anyway. Happy to wait and see if it leads to something a bit more though.
Lets make sure that no one will ever want to dev for us anymore by slapping the new guy around who took the time to try something himself. I recall Paul didnt have enough posts to start a thread in dev but he seems to know what hes doing. Why not just ban anyone whos new from ever posting any kind of dev work ever. Because what we need are more people making fun of and trashing someones work instead of people actually willing to take their time and try to make YOUR device nicer. Any wonder if this is why devs are leaving xda every day?
BTW..Just flashed this and it booted just fine. I did a system wipe first.
Maybe you should be the guy to add onskreen framework to a rom....hint
DTgreat said:
Yes, although like I said. I know what I am doing. My power cord in fact, may have just broke. (Although I doubt it.)
Click to expand...
Click to collapse
It's possible. I've had a few reports of it working so far.
KingDavid63 said:
IF YOU cant post links yet it's for a reason
Click to expand...
Click to collapse
I know. It was because my post count was too low.
timbit123 said:
cool, where did you get the source code from asus?
Click to expand...
Click to collapse
I didn't, sadly. I kludged it together somewhat by dding the fully updated ICS /system partition(adding busybox, su, Superuser beforehand) and making it into a blob that's flashable.
robojerk said:
It sounds like he got the ROM and removed the third party apps, not that he got the source code to build it to AOSP.
Click to expand...
Click to collapse
Correct.
Thanks for the feedback guys. If you want anything added, I'll try to accomodate with flashable zips since they're smaller to upload. My upload is horrible, so I can only upload a large ROM every once in a while(it takes over an hour!). I'm not discouraged, I know how it is to be the new guy. I know this rom's probably nothing special, but I just wanted to share what I'm enjoying with others.
daxtsu said:
Yes, why? It worked fine on my TF101.
Click to expand...
Click to collapse
Hey man at least you are the first to have out a custom rom, can't wait to test it out later
Sent from eee pad Transformer running ICS
Lantek23 said:
Hey man at least you are the first to have out a custom rom, can't wait to test it out later
Sent from eee pad Transformer running ICS
Click to expand...
Click to collapse
Haha, it's not that custom, more of a repack with a bunch of removed apps, but I'll look into making it deodexed and stuff. I'm still learning how to do that.
Popping into a best buy and trying a different power cord when my friend gets here. Not trying to naysay. Just trying to troubleshoot.
DTgreat said:
Popping into a best buy and trying a different power cord when my friend gets here. Not trying to naysay. Just trying to troubleshoot.
Click to expand...
Click to collapse
Oh, I know. It's cool.
Hope you get it sorted out soon.
I'll try it out later (I got too many projects going on), but I appreciate your contribution.
As someone who has been around these forums and been messing around with ROMs for a while now (but has never posted before), I applaud the effort. THANKS.
Q&A for [ROM][2.3.6] AEON v1.4SL STABILITY AT ITS FINEST
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][2.3.6] AEON v1.4SL STABILITY AT ITS FINEST. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Where to go from here
Not sure what happened, hope this didn't get posted twice.
Hi,
I am still happily using the Samsung Infuse 4G, and was running the stock GB 2.3.6. No real issues, and although starting to get a sense of it being dated was having no issues and in no rush to go out and upgrade. However, we recently purchased a 2015 Subaru Legacy with their Starlink multimedia system. The Infuse, as it was with the stock GB had no problems connecting via BT for phone and audio functionality. But, the car system reports that the phone is not compatible for messaging. In my endeavors to understand why, I thought, maybe incorrectly, that GB does not support the MAP profile.
So, that led me to, is it possible to add that, and how do you do it, or is it time to upgrade? Flash a new ROM? I can't seem to find much on the specific issue I am trying to resolve and if a new ROM would fix it, but since the phone is way out of warranty I decided to try rooting and flashing a ROM. I am new to this so I went with the Aeon 1.4 ROM based on GB 2.3.6 (I think), hoping that it was a bit less risky. Everything went well and seems to be working fine. But, it did not fix the messaging issue with the car. I assume because it is really still GB.
Am I going about this wrong? Would a flash up to ICS or beyond possibly do it? I am not totally against a new phone, but till now I wasn't even thinking about a new phone. Suggestions? Which ICS, or other ROM would you recommend? Thanks all.
Hi there,
mainwheel said:
Would a flash up to ICS or beyond possibly do it? I am not totally against a new phone, but till now I wasn't even thinking about a new phone. Suggestions? Which ICS, or other ROM would you recommend? Thanks all.
Click to expand...
Click to collapse
I think your car requires the newest bluetooth protocol (4.0), something that is primarily hardware based.
I could be (and hopefully am) wrong here, but the only way to find out is to do a ROM walkabout.
ICS is out right off the bat, as bluetooth was borked in that version (IIRC). You'll need to upgrade to that in the process anyway, as CWM for this device doesn't like drastic changes.
I am biased, but I would try CarbonROM 4.4.4 (the latest, unofficial build) or at the very least CM 10.1. The former would have the best chance of support (being latest firmware available), but it may be overkill for your situation (newer versions = harder on battery life).
So I would try CM 10.1 after stepping up to ICS (having done a full nandroid before all this), and if the car still refuses to connect, try Carbon. Then you may be able to prove me wrong.
Hope this helps.
Sent from my MeMO Pad 8"
joel.maxuel said:
Hi there,
I think your car requires the newest bluetooth protocol (4.0), something that is primarily hardware based.
I could be (and hopefully am) wrong here, but the only way to find out is to do a ROM walkabout.
ICS is out right off the bat, as bluetooth was borked in that version (IIRC). You'll need to upgrade to that in the process anyway, as CWM for this device doesn't like drastic changes.
I am biased, but I would try CarbonROM 4.4.4 (the latest, unofficial build) or at the very least CM 10.1. The former would have the best chance of support (being latest firmware available), but it may be overkill for your situation (newer versions = harder on battery life).
So I would try CM 10.1 after stepping up to ICS (having done a full nandroid before all this), and if the car still refuses to connect, try Carbon. Then you may be able to prove me wrong.
Hope this helps.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
Thanks very much for your reply.
Being a hardware issue is something I have considered, but not knowing enough to understand why it might work virtually flawlessly for phone and audio streaming in the car, I was hopeful the hardware would support additional Bluetooth profiles, that are added with a new ROM. But then again, I would not be surprised to do the walkabout and end up at the store for a new phone in the end anyway.
I will be looking for an ICS ROM, but it sounds like it doesn't matter which one I use because I won't be staying there?
I have done, and will do again, backups, but I am little unclear on a few things. CWM is on the phone, but I actually used ROM Manager for the flashing I've done. Are they the same thing? It uses CWM. Also, I've seen various references to making sure the phones identity (not sure that's the right term) is saved, and I take that to mean that after flashing the phone may no longer be able to access phone carrier service. Is that a real possibility? And, is it necessary to remove the SD card? Thanks again.
mainwheel said:
Thanks very much for your reply.
Being a hardware issue is something I have considered, but not knowing enough to understand why it might work virtually flawlessly for phone and audio streaming in the car, I was hopeful the hardware would support additional Bluetooth profiles, that are added with a new ROM. But then again, I would not be surprised to do the walkabout and end up at the store for a new phone in the end anyway.
I will be looking for an ICS ROM, but it sounds like it doesn't matter which one I use because I won't be staying there?
I have done, and will do again, backups, but I am little unclear on a few things. CWM is on the phone, but I actually used ROM Manager for the flashing I've done. Are they the same thing? It uses CWM. Also, I've seen various references to making sure the phones identity (not sure that's the right term) is saved, and I take that to mean that after flashing the phone may no longer be able to access phone carrier service. Is that a real possibility? And, is it necessary to remove the SD card? Thanks again.
Click to expand...
Click to collapse
I would recommend Entropy's ICS build, which I have a mirror of, accessed from my signature link.
ROM manager loads CWM (same author, ROM manager is IIRC just the Play Store delivery mechanism for CWM), so once you have CWM, you are good to go for your walkabout.
Yes, you want to make sure to back up your IMEI information first, because that stuff can get lost, which if lost, will deny you access to your carrier. There is a way to retrieve it if lost on this device, but an ounce of prevention is worth a pound of cure. Check the CM10.x thread on instructions how to flash (with links to the IMEI backup).
No need to remove the SD card, but if you don't need it for a flash, I would remove it anyway (or back up it's contents to your PC first - in case in the unlikely event - I'm paranoid about those things - CWM goes a little liberal with the factory reset).
Hope this helps.
joel.maxuel said:
I would recommend Entropy's ICS build, which I have a mirror of, accessed from my signature link.
ROM manager loads CWM (same author, ROM manager is IIRC just the Play Store delivery mechanism for CWM), so once you have CWM, you are good to go for your walkabout.
Yes, you want to make sure to back up your IMEI information first, because that stuff can get lost, which if lost, will deny you access to your carrier. There is a way to retrieve it if lost on this device, but an ounce of prevention is worth a pound of cure. Check the CM10.x thread on instructions how to flash (with links to the IMEI backup).
No need to remove the SD card, but if you don't need it for a flash, I would remove it anyway (or back up it's contents to your PC first - in case in the unlikely event - I'm paranoid about those things - CWM goes a little liberal with the factory reset).
Hope this helps.
Click to expand...
Click to collapse
Thanks Joel. I have now installed Entropy. Don't know whether everything else is working, but I do know that I can not connect to my wifi. Keep getting "authentication problem." I see that it is a known problem, but I'm not finding a solution. Not quite ready to go the next step (time constraint), so I'm hoping there is a fix, or at least a workaround. Kind of a bummer not having access to wifi. Any suggestions?
mainwheel said:
Thanks Joel. I have now installed Entropy. Don't know whether everything else is working, but I do know that I can not connect to my wifi. Keep getting "authentication problem." I see that it is a known problem, but I'm not finding a solution. Not quite ready to go the next step (time constraint), so I'm hoping there is a fix, or at least a workaround. Kind of a bummer not having access to wifi. Any suggestions?
Click to expand...
Click to collapse
I wouldn't worry about it. Entropy is just a step-through (because BlueTooth is broken as well) and there are other ways to get the other ROMs onto the device (if they are not there already) such as adb push or MicroSD + Built-in Filemanager App. Higher versions will have that fixed anyway.
Downloadable CM 10.1
joel.maxuel said:
I wouldn't worry about it. Entropy is just a step-through (because BlueTooth is broken as well) and there are other ways to get the other ROMs onto the device (if they are not there already) such as adb push or MicroSD + Built-in Filemanager App. Higher versions will have that fixed anyway.
Click to expand...
Click to collapse
Thanks again Joel.
I don't have a lot on my data plan, so I rely on wifi quite a bit. But for now, not a big deal and will try to upgrade asap. No issues with getting the file to the phone, but I am having some difficulty finding a downloadable CM 10.1 (actually it is 10.2), and a gapps file for it. The XDA forum I went to doesn't work and if I go to the mirror site it tells me the file is too big or something and I'm not able to download. Haven't scoured the internet looking for it, thought I might save some time if you know where I can get it. If not, I'm thinking just try the Carbon ROM, assuming I can find it. I know you recommend CM first. George
mainwheel said:
Thanks again Joel.
I don't have a lot on my data plan, so I rely on wifi quite a bit. But for now, not a big deal and will try to upgrade asap. No issues with getting the file to the phone, but I am having some difficulty finding a downloadable CM 10.1 (actually it is 10.2), and a gapps file for it. The XDA forum I went to doesn't work and if I go to the mirror site it tells me the file is too big or something and I'm not able to download. Haven't scoured the internet looking for it, thought I might save some time if you know where I can get it. If not, I'm thinking just try the Carbon ROM, assuming I can find it. I know you recommend CM first. George
Click to expand...
Click to collapse
Hi George,
My signature link contains the CM10.1 ROM (and Gapps) as well. I had problems with CM10.2 back in the day (wouldn't install), so I would recommend 10.1 over 10.2.
My Dropbox may be exhausted for the day (sometimes it gets like that) but I may have a copy on well, Copy, that I could send if necessary. Just let me know if you have problems downloading from my mirror first.
joel.maxuel said:
Hi George,
My signature link contains the CM10.1 ROM (and Gapps) as well. I had problems with CM10.2 back in the day (wouldn't install), so I would recommend 10.1 over 10.2.
My Dropbox may be exhausted for the day (sometimes it gets like that) but I may have a copy on well, Copy, that I could send if necessary. Just let me know if you have problems downloading from my mirror first.
Click to expand...
Click to collapse
Joel,
Maybe I'm just missing something. Not having a problem downloading, I'm having a problem finding the files to download.
The only link I find (it's the link that says something about development files?) takes me to the XDA CM 10.2 forum where I wasn't able to get it. Maybe I'm just missing it in your signature links. I see references to Carbon and other stuff. George
mainwheel said:
Joel,
Maybe I'm just missing something. Not having a problem downloading, I'm having a problem finding the files to download.
The only link I find (it's the link that says something about development files?) takes me to the XDA CM 10.2 forum where I wasn't able to get it. Maybe I'm just missing it in your signature links. I see references to Carbon and other stuff. George
Click to expand...
Click to collapse
George,
Each list item has two links....the original source item (thread), and then the dropbox download link (labelled "download") so you are looking for this.
Hope this helps.
joel.maxuel said:
George,
Each list item has two links....the original source item (thread), and then the dropbox download link (labelled "download") so you are looking for this.
Hope this helps.
Click to expand...
Click to collapse
DOH! Didn't even see that there were two links. Sorry about that. Think I've got everything now, and can find it again if I need it. Now to do the work. Thanks for your help. Will let you know how it goes. George
mainwheel said:
DOH! Didn't even see that there were two links. Sorry about that. Think I've got everything now, and can find it again if I need it. Now to do the work. Thanks for your help. Will let you know how it goes. George
Click to expand...
Click to collapse
Hi Joel,
Got it upgraded to CM 10.1. All seems well. Unfortunately, it did not fix the compatibility problem with messaging and our car, as you correctly suggested might happen. Is there anything about Carbon that gives you reason to think it might work? As I said in the original post, I made some assumptions about the problem (Bluetooth MAP profile based on some reading), and that might be a software fix. But, of course, I may be completely wrong about it. Thanks. George
mainwheel said:
Hi Joel,
Got it upgraded to CM 10.1. All seems well. Unfortunately, it did not fix the compatibility problem with messaging and our car, as you correctly suggested might happen. Is there anything about Carbon that gives you reason to think it might work? As I said in the original post, I made some assumptions about the problem (Bluetooth MAP profile based on some reading), and that might be a software fix. But, of course, I may be completely wrong about it. Thanks. George
Click to expand...
Click to collapse
Hello again George,
Nothing about Carbon in general, but KitKat, yes...
Android 4.4 support for two new Bluetooth profiles to let apps support a broader range of low-power and media interactions. Bluetooth HID over GATT (HOGP) gives apps a low-latency link with low-power peripheral devices such as mice, joysticks, and keyboards. Bluetooth MAP lets your apps exchange messages with a nearby device, for example an automotive terminal for handsfree use or another mobile device. As an extension to Bluetooth AVRCP 1.3, users can now set absolute volume on the system from their Bluetooth devices.
Click to expand...
Click to collapse
Gone this far, might as well give it a shot. :fingers-crossed:
joel.maxuel said:
Hello again George,
Nothing about Carbon in general, but KitKat, yes...
Gone this far, might as well give it a shot. :fingers-crossed:
Click to expand...
Click to collapse
I guess it couldn't stay easy. My attempt to install CARBON (two different download versions) failed, I am getting an error I don't understand.
First, when I go to wipe dalvik I get E: unknown volume for .... (/sd-ext) I can not read it very well because of the background image. Where I put the ... it looks like path.
Then
This ROM uses an imcompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
Then
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/CARBON-KK-NIGHTLY-20141102-0915-infuse4g.zip
(Status 7)
Installation aborted.
Any ideas what this means? I can reload CM 10.1, so I am not bricked or anything. I appreciate your help.
I did try to get some help from the IRC forum at CARBON, but haven't gotten any replies.
George
mainwheel said:
I guess it couldn't stay easy. My attempt to install CARBON (two different download versions) failed, I am getting an error I don't understand.
First, when I go to wipe dalvik I get E: unknown volume for .... (/sd-ext) I can not read it very well because of the background image. Where I put the ... it looks like path.
Then
This ROM uses an imcompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
Then
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/CARBON-KK-NIGHTLY-20141102-0915-infuse4g.zip
(Status 7)
Installation aborted.
Any ideas what this means? I can reload CM 10.1, so I am not bricked or anything. I appreciate your help.
I did try to get some help from the IRC forum at CARBON, but haven't gotten any replies.
George
Click to expand...
Click to collapse
There's this tutorial (section 27), but what may be happening is a drastic change in ROM's for CWM (which falls under what status 7 error scope - along with corrupted IMEI, etc).
My upgrade path long ago (coincidentally) was Stock -> CM9 -> CM10.1 -> Beanstalk 4.4.2 -> CarbonROM 4.4.4.
You can, however cheat, by disabling voodoo lagfix in CWM settings. Otherwise, you may need to find the oldest CarbonROM Kitkat you can grab (4.4.2), to make that last (small) jump to 4.4.4.
If still doesn't work, roll back to CM10.1, make sure everything is order (including calling), and try again.
joel.maxuel said:
There's this tutorial (section 27), but what may be happening is a drastic change in ROM's for CWM (which falls under what status 7 error scope - along with corrupted IMEI, etc).
My upgrade path long ago (coincidentally) was Stock -> CM9 -> CM10.1 -> Beanstalk 4.4.2 -> CarbonROM 4.4.4.
You can, however cheat, by disabling voodoo lagfix in CWM settings. Otherwise, you may need to find the oldest CarbonROM Kitkat you can grab (4.4.2), to make that last (small) jump to 4.4.4.
If still doesn't work, roll back to CM10.1, make sure everything is order (including calling), and try again.
Click to expand...
Click to collapse
Thanks again Joel.
I may have to bag this whole project. Must be a little late doing this. Too much time and trouble searching for files that can't be downloaded. I could not find an early CarbonROM KitKat to download. I could not find a BeanStalk to download. I find links that point to a defunct website. I did finally find a CM11 which I did download, but I did not see a gapps file to go with it, unless I can use any 4.4 gapps. Also, when I run CWM there is no reference to lagfix. I appreciate all the help, but I don't want to take any more of your time. George
mainwheel said:
Thanks again Joel.
I may have to bag this whole project. Must be a little late doing this. Too much time and trouble searching for files that can't be downloaded. I could not find an early CarbonROM KitKat to download. I could not find a BeanStalk to download. I find links that point to a defunct website. I did finally find a CM11 which I did download, but I did not see a gapps file to go with it, unless I can use any 4.4 gapps. Also, when I run CWM there is no reference to lagfix. I appreciate all the help, but I don't want to take any more of your time. George
Click to expand...
Click to collapse
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
joel.maxuel said:
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
Click to expand...
Click to collapse
Thanks Joel. I appreciate the help and will try to make some time to install these files. Will let you know. George
joel.maxuel said:
Hi George,
Any 4.4.2 Gapps will work. I am uploading one right now (along with older Beanstalk and CM11)...
https://www.dropbox.com/sh/smohomrdx0oqn76/AACfrsgXTEHhDmVtwEWj6EA5a?dl=0
...it may take an hour for files to appear, so keep posted, if still interested.
Also, another way to disable voodoo lagfix (if not found in CWM) is to create a folder on internal storage called Voodoo, and then a folder inside that called disable-lagfix.
Hope this helps.
Click to expand...
Click to collapse
Hi Joel,
Unfortunately, none of these 4.4.x versions will install, same error. And placing Voodoo/lagfix/ folder doesn't seem to work either, same error. If the problem is the jump to the next version is too great, maybe an earlier version of something, 4.2 or earlier? George