Related
Just throwing an idea out there, and since it's for developers (specifically people who make their own recovery images) I assume this is the right section.
Since we have 'control' over the recovery image on our phones, would it not be possible to add a little script to an update.zip that a suitably modified recovery image could extract and run to interactively prompt the user for various Rom options? I'm thinking specifically of kernel choices, but it could be extended to almost anything that needs to be done prior to booting the installed image.
Imagine installing a rom, and during the install you got a little menu like this:
1: RamHack, BFS Kernel
2: RamHack, CFS Kernel
3: No-RamHack, BFS....
etc...
inefficient, it adds extra baggage to rom, and more things can go wrong. what would you rather downlaod a 90mb file or a 110 mb file.
Which would you rather download, one 110MB ROM or 2 90MB ROMS?
I'm pretty sure there's more than a few people who'll download different variations of the same ROM so they can see which is faster, how much easier would it be to just download one thing and then choose which options you want in there without downloading anything else.
I believe it is entirely possible. As a matter of fact, I was working on a ROM project that would have an interactive installer from the update.zip that would selectively install different features, apps, customization, themes, etc., based on the recovery menu application. It would use a lot of the /cache for temp space, though, as the installer application and its resources and configuration file, and later, the necessary parts of the ROM itself, would need to be unzipped before the install can run, if I recall correctly.
Does anyone have a good link to a reference for the command syntax for the /META-INF/com/google/android/update-script file? I'll go search for it in a few moments myself. I could probably make a simple ROM installer that chooses between ROM X and ROM Y based on a key input, as a proof of concept. I'll test it myself, I don't really mind half-bricking my device for science. (As long as I don't need to touch the SPL/Radio, that is.)
Update: Some creative searching finds me this:
JesusFreke said:
Assuming you mean update-script in an update.zip update, you will need to either look at existing update-script files for an example of the syntax, or look at the source of the recovery program in the android source
Click to expand...
Click to collapse
There's also a "make-update-script.c" file I'm seeing here and there, I'm trying to find the file in the Android source.
Update 2: From install.c at donut from cyanogen's android_bootable_recovery:
Code:
#define ASSUMED_UPDATE_SCRIPT_NAME "META-INF/com/google/android/update-script"
#define ASSUMED_UPDATE_BINARY_NAME "META-INF/com/google/android/update-binary"
and in commands.c, toward the bottom at register_update_commands is all the commands defined, and above that are all the functions they carry out.
sorry about that deicist i was sleepy when i wrote that so i must have been cranky yea i guess that is a fine idea, with just 30 more mb you have like 300mb worth of stuff. and you can pick which 90 mb you want.
markolo25 said:
sorry about that deicist i was sleepy when i wrote that so i must have been cranky yea i guess that is a fine idea, with just 30 more mb you have like 300mb worth of stuff. and you can pick which 90 mb you want.
Click to expand...
Click to collapse
Well, on the 32B platform with the Death SPL (my phone) we have the following partitions of the internal NAND memory (mtdblock*) from the df and mount command:
NAND 3: /system 92160kb - OS partition, static and read-only
NAND 5: /data 91904kb - User, system config, app config, and apps (without a2sd)
NAND 4: /cache 30720kb - OTA cache, Recovery/update config and temp
And I'd assume NAND 1 and 2 are the kernel, ramdisk, and bootloader config.
So the ROM wouldn't exceed 92MB installed (most leave some room in /system for hacks and updates). And the update process doesn't ever really "flash", per se; it just formats, copies files, and sets permissions and initialization configs, like Windows or Mac.
So the files that are common to the different ROMs being packaged don't need to be duplicated, only the ones that are changed (like a boot.img, or 32A/B compatibility, or different apps). The update script and chooser menu will decide which files to copy. Meaning the ROM package in and of itself shouldn't really need to exceed 128MB, even if choosing from a wide variety of platforms. And upon installation, the system might take less than 32 MB.
yeah, what he said ^
The scenario I was thinking about specifically was SuperD. If you look here:
http://forum.xda-developers.com/showthread.php?t=613809
There's 8 different downloads there. How many files are actually different between those 8? I guess the themes mean a lot of application files are different (due to having different resources in them) but the underlying framework files will be pretty much the same I think.
Deicist said:
yeah, what he said ^
The scenario I was thinking about specifically was SuperD. If you look here:
http://forum.xda-developers.com/showthread.php?t=613809
There's 8 different downloads there. How many files are actually different between those 8? I guess the themes mean a lot of application files are different (due to having different resources in them) but the underlying framework files will be pretty much the same I think.
Click to expand...
Click to collapse
I could download them all, and find the differences of each. It would be cool if a ROM like this were available in a single download, from which you would choose the content from the device before flashing.
Also, inspired by talking about this, I wrote up a guide on the update-script in the package file. It's still not finished, but it'll be the only guide available for that syntax yet (trust me, I couldn't find one myself ). Link's in my sig.
I'm surprised that nobody's mentioned the Droid... the sholes.info rom (now called droidmod) have used a .tgz archive instead of a .zip, the .tgz installs have always allowed this customization, droidmod makes one of the most common recovery's AND rom's. (SPRecovery/Droidmod).
It give you the option to choose what launcher to install, what theme, what apps to remove.
page here: http://droidmod.org/news/droidmod-v1-0-is-out/
how big of a ROM are you thinking about?
There are roms (WG etc...) that offer more than one kernel as update.zip you can flash over an existing installation of your rom instead of adding all the stuff to one big file. also you can download themes for several roms/for metamorph.
so why would you want some big install script instead of just downloading the files you like and flash it?
jmhalder said:
I'm surprised that nobody's mentioned the Droid... the sholes.info rom (now called droidmod) have used a .tgz archive instead of a .zip, the .tgz installs have always allowed this customization, droidmod makes one of the most common recovery's AND rom's. (SPRecovery/Droidmod).
It give you the option to choose what launcher to install, what theme, what apps to remove.
page here: http://droidmod.org/news/droidmod-v1-0-is-out/
Click to expand...
Click to collapse
Is the Droid's recovery image capable of running on the G1, and/or is it open-source enough to be cross-built to the G1? If so, we could port it here. Only problem there though, is that all the roms are in update.zip format for the G1 already, we'd need to make it dual-compatible if we don't want to split the community and annoy generally everyone ("My rom only supports TGZ recovery!" "ROMs are in ZIP format, and I will not make a TGZ one for those unfortunate enough to use the other Recovery!")
domenukk said:
There are roms (WG etc...) that offer more than one kernel as update.zip you can flash over an existing installation of your rom instead of adding all the stuff to one big file. also you can download themes for several roms/for metamorph.
so why would you want some big install script instead of just downloading the files you like and flash it?
Click to expand...
Click to collapse
Well, for one, devs need to host one file only, and users need to download one file only. The file won't be much bigger or more complex at all, really. And the way things look on the recovery side, we could probably put a selection of themes in with the updater and patch them in post-install with a Metamorph script straight from recovery. That way, the rom is as you want it out-of-the-box, no multiple reboots, etc.
Also, those scripts that usually run on first-boot, like zipalign, dexopt, apps2sd etc. should run from the recovery environment, instead of before the Android bootanimation (I do get tired of hearing "This ROM will take a LONG time on the first boot. If it's stuck at the G1 screen, just wait 10-30 minutes.")
So what would you rather have, one single ROM (G1_Android_ROM_v1.17.zip) for each version released,
or six different ZIPs to flash (G1_Android_ROM_10MB_CFS.zip, G1_Android_ROM_Greentheme.zip, G1_Android_ROM_Bluetheme.zip, G1_Android_Nowipe_GApps.zip)?
Would you rather select what you want to include at flash (and be able to change things like themes or features after flashing), or have 20 different files to choose from, wiping and flashing on each?
I am aware of the no-wipe upgrades for many ROMs, but they can get confusing (I once flashed a CFS_10MB.zip that was for a Hero ROM, stupidly thinking that it might have been for the Eclair that I just downloaded.) Needless to say, I had to wipe and reflash. Again.
TylTru said:
Is the Droid's recovery image capable of running on the G1, and/or is it open-source enough to be cross-built to the G1? If so, we could port it here. Only problem there though, is that all the roms are in update.zip format for the G1 already, we'd need to make it dual-compatible if we don't want to split the community and annoy generally everyone ("My rom only supports TGZ recovery!" "ROMs are in ZIP format, and I will not make a TGZ one for those unfortunate enough to use the other Recovery!")
Well, for one, devs need to host one file only, and users need to download one file only. The file won't be much bigger or more complex at all, really. And the way things look on the recovery side, we could probably put a selection of themes in with the updater and patch them in post-install with a Metamorph script straight from recovery. That way, the rom is as you want it out-of-the-box, no multiple reboots, etc.
Also, those scripts that usually run on first-boot, like zipalign, dexopt, apps2sd etc. should run from the recovery environment, instead of before the Android bootanimation (I do get tired of hearing "This ROM will take a LONG time on the first boot. If it's stuck at the G1 screen, just wait 10-30 minutes.")
So what would you rather have, one single ROM (G1_Android_ROM_v1.17.zip) for each version released,
or six different ZIPs to flash (G1_Android_ROM_10MB_CFS.zip, G1_Android_ROM_Greentheme.zip, G1_Android_ROM_Bluetheme.zip, G1_Android_Nowipe_GApps.zip)?
Would you rather select what you want to include at flash (and be able to change things like themes or features after flashing), or have 20 different files to choose from, wiping and flashing on each?
I am aware of the no-wipe upgrades for many ROMs, but they can get confusing (I once flashed a CFS_10MB.zip that was for a Hero ROM, stupidly thinking that it might have been for the Eclair that I just downloaded.) Needless to say, I had to wipe and reflash. Again.
Click to expand...
Click to collapse
You could just have flashed the original rom without wipe.
Would be a step forward if you could simply put roms and additional files in folders... maybe even whole zip files containing some updates and an xml like file to describe them. This would guarantee compatibility with earlier boot images (just unpack the updates in the zip). Tar might work better than zip as it is not compressed thus faster afaik.
http://droidninja.com/?p=26334
We got ninja'd. Apparently the Droid Does exactly this.
So let's get to work on porting it! Like this comment says, I'm working on finding the source code to a good Droid recovery image (sadly Droid hasn't its own forum here), and if it's closed source, I'll get on reverse-engineering a .tgz rom to see exactly how it works.
TylTru said:
http://droidninja.com/?p=26334
We got ninja'd. Apparently the Droid Does exactly this.
So let's get to work on porting it! Like this comment says, I'm working on finding the source code to a good Droid recovery image (sadly Droid hasn't its own forum here), and if it's closed source, I'll get on reverse-engineering a .tgz rom to see exactly how it works.
Click to expand...
Click to collapse
This is pretty awesome. I was going to say, we could easily run bash scripts but this is so much better.
This needs to be merged with both Amon_ra's recovery and the new 2.x based recovery...
...............................................
.....................................
.........................................
`````````````
nice job...try it now!...i saw it on twitter two days ago...
zhang yixi said:
nice job...try it now!...i saw it on twitter two days ago...
Click to expand...
Click to collapse
Okay cool, Let me know how you like it and if you got any problems just post and i will get to them
Fastest way to send a bug is with twitter
LOL i am a twitter addict and have it refreshing every 5 minutes haha
And which is the default frequency? 528? Or...
Anyway, flashing right now. I LOVE ur Roms.... hehehe
Just flash.
I feel abit slower than cm5.0.7 test3.
Thanks for the hard work.
Hello New Thread.
I kinda figured you fell asleep last night Kolohe. I will check your beta when I get home from work later today and put up the mirror. I am going to keep your old ROMs up there too
got a question.
Did a total wipe and when it booted up first time, I got a low space warning. Apparently a whole bunch of my apps that were on SDcard came back as installed. And because on first boot, apps2sd isn't on yet, it tried to put them on internal (I had about +/- 80 apps come back from my 139 total)
So I backed out, rewiped data, dalvik, and ext, and reflashed rom. It boot up fine again, but once again, it immediately installed 7 of the apps (replica island, docs to go, pobs... just to name a few). So I moved them to sd card and all is fine.
The question is:
1. Is this normal? I've never had this happen before CM5 based ROMs. I haven't tried any other Eclair roms except the CM5 based ones and I wasn't sure if this is a behavior that's normal for 2.1 roms.
2. Why only some of the apps come back? Isn't wiping ext supposed to clear it all out or am I mistaken?
Just wanted to let you know, there seems to be a problem with using Backup for Root users. It will break any apps allready installed and fix_permissions or Repair ext will not help, I have found this to be true on all CY5 based roms.
EDIT:Restoring SMS,Call log and even Market DB seems to work fine after running Fix_permissions, Restoring APPS Does Nothing.(No APPS Restored) It Was trying use the Dusted-donuts hack that caused the apps to be Broken.
EDIT:::: The problem WITH APPS NOT WORKING APPEARS TO HAVE BEEN CAUSED BY ME TRYING TO USE THE JIT HACK "DUSTED-DONUTS" LIKE I DID WITH 4.1. I believe the JIT Flash Update for Cy5 will work though.
EDIT: JIT-HACK It does work.http://droidbasement.com/db-blog/?p=245 this is what i used.
Thanks again for a great rom!
This thing Flies!
I'm using the Jit-Hack And AnyKernel OC Patch,changed swappiness to 95 in 86supersettings,and cpu refresh to 1000000(kills batt),and Cpu Min/Max to 122800/716000. Still using SetCPU for Sleep/failsafe Profile.
EDIT2: I just noticed that at the initial google sign in screen you can press menu and in addition to the normal Wireless settings option there is now an option to disable auto restore!( I know you probably already knew that and it has been mentioned a hundred times!)
well gonna give this a try let u know soon for any bugs
To confirm this is JACP?
Watching logcat I saw that debugger daemon is enabled. I/Debug.
and is this based on CE-5.0 t2? or are patches for T3 in place?
quick question:
If I extracted the boot img from this rom and flashed it with my currently installed CM 5.0.7 test 3 would it still have the same speed boost, optimization, and cache clearing settings?
Not that I don't want to flash this rom itself, but I was just wondering if I could also try out the features with another.
Will fix the apparently problem but that might be caused by thenew boot script that wipes the dalvik cache. .. will be working on that later today
quick question:
If I extracted the boot img from this rom and flashed it with my currently installed CM 5.0.7 test 3 would it still have the same speed boost, optimization, and cache clearing settings?
Not that I don't want to flash this rom itself, but I was just wondering if I could also try out the features with another.
Click to expand...
Click to collapse
You can I suppose,
Just needs to be a CM5 based rom
Just wanted to let you know, there seems to be a problem with using Backup for Root users. It will break any apps allready installed and fix_permissions or Repair ext will not help, I have found this to be true on all CY5 based roms.
EDIT:Restoring SMS,Call log and even Market DB seems to work fine after running Fix_permissions, it is just trying to restore apps that messes it up.
EDIT:::: The problem WITH APPS NOT WORKING APPEARS TO HAVE BEEN CAUSED BY ME TRYING TO USE THE JIT HACK "DUSTED-DONUTS" LIKE I DID WITH 4.1. I believe the JIT Flash Update for Cy5 will work though.
Also as a side note, I think apps2sd must be enabled by default,or get rid of the auto app restore thing. I think it is going to confuse people and clutter up the threads.
But thanks again for a great rom!
EDIT2: I just noticed that at the initial google sign in screen you can press menu and in addition to the normal Wireless settings option there is now an option to disable auto restore!( I know you probably already knew that and it has been mentioned a hundred times!)
Click to expand...
Click to collapse
Ohh. I think I might know why that is happening and I think I night be able to fix that.... but seeing that I don't use it I might need to find a tester to see if it works
got a question.
Did a total wipe and when it booted up first time, I got a low space warning. Apparently a whole bunch of my apps that were on SDcard came back as installed. And because on first boot, apps2sd isn't on yet, it tried to put them on internal (I had about +/- 80 apps come back from my 139 total)
So I backed out, rewiped data, dalvik, and ext, and reflashed rom. It boot up fine again, but once again, it immediately installed 7 of the apps (replica island, docs to go, pobs... just to name a few). So I moved them to sd card and all is fine.
The question is:
1. Is this normal? I've never had this happen before CM5 based ROMs. I haven't tried any other Eclair roms except the CM5 based ones and I wasn't sure if this is a behavior that's normal for 2.1 roms.
2. Why only some of the apps come back? Isn't wiping ext supposed to clear it all out or am I mistaken?
Click to expand...
Click to collapse
Yes it is normal but if you want to turn it off before you log in press menu button in setup andthere should be an option to turn it off
Ohh. I think I might know why that is happening and I think I night be able to fix that.... but seeing that I don't use it I might need to find a tester to see if it works
Click to expand...
Click to collapse
I would be willing to test any of your ROMs that would help you out. I am good at BART Backup and Restore! Just let me know.
Ohh. I think I might know why that is happening and I think I night be able to fix that.... but seeing that I don't use it I might need to find a test
Click to expand...
Click to collapse
I would be willing to test any of your ROMs that would help you out. I am good at BART Backup and Restore! Just let me know.
Click to expand...
Click to collapse
Okay when I get home I willtry and fix
Guys, I just got my XT720 and I'm going to either flash it for Wanted's froYo or keep stock Eclair + Jit and App2SD. From what I read, wanted's lastest ROM seems the best option for me me once I don't use Wi-Fi, but I got some questions that I din't find in the release topic:
1. Does the native App2SD for FroYo works?
2. Flash Player Works?
3. If the native APP2SD doens't works, can I apply this method :http://forum.xda-developers.com/showpost.php?p=7909401&postcount=52 on this ROM, or if I do this before flash for 2.2 will it keep JIT em App2SD?
4. How do I check wich stock ROM I'm using? I just got the phone, bought it in USA, but I guess it's the Euro version coz MotoNav has only Euro maps.
I guess is it, thanks in advice.
Lezherus said:
Guys, I just got my XT720 and I'm going to either flash it for Wanted's froYo or keep stock Eclair + Jit and App2SD. From what I read, wanted's lastest ROM seems the best option for me me once I don't use Wi-Fi, but I got some questions that I din't find in the release topic:
1. Does the native App2SD for FroYo works?
2. Flash Player Works?
3. If the native APP2SD doens't works, can I apply this method :http://forum.xda-developers.com/showpost.php?p=7909401&postcount=52 on this ROM, or if I do this before flash for 2.2 will it keep JIT em App2SD?
4. How do I check wich stock ROM I'm using? I just got the phone, bought it in USA, but I guess it's the Euro version coz MotoNav has only Euro maps.
I guess is it, thanks in advice.
Click to expand...
Click to collapse
1. yes
2. yes
3. I know Dexters ROMs will automatically move the user apps to an ext2(3?) partition if it's there. In addition Mioze7Ae patch to 1.3 offers additional configurations as to how this works, I'm not sure about XAVs ROMS in this respect.
I am watching XAVs ROMs & once he fixes the bugs in the 1.3 beta I'll be giving it a try. Kahlpowers also has some nice themed variations, you can check out his builds in his post in the theme section (you'll want to look towards the end of the thread as the themes at the beginning are based on 2.1 eclair).
HTH
3rdstring said:
1. yes
2. yes
3. I know Dexters ROMs will automatically move the user apps to an ext2(3?) partition if it's there. In addition Mioze7Ae patch to 1.3 offers additional configurations as to how this works, I'm not sure about XAVs ROMS in this respect.
I am watching XAVs ROMs & once he fixes the bugs in the 1.3 beta I'll be giving it a try. Kahlpowers also has some nice themed variations, you can check out his builds in his post in the theme section (you'll want to look towards the end of the thread as the themes at the beginning are based on 2.1 eclair).
HTH
Click to expand...
Click to collapse
Thank you very much, so I'll just flash Dexter's or Xav's ROM. I'll read a bit more about Dexter's lastest release, I was going to try Xav's coz people said it's faster than Dexter's and actually the only bugs reported aren't that bad ( at least for me) but Dexter's maybe a better option while Xav's doesn't fix all bugs. Thanks again =)
Guys, I flashed my phone to Dexter's 1.3 ROM, it's working fine, but I have "2" new questions:
1. I want install that Honeycomb Theme from Kahpower http://forum.xda-developers.com/showpost.php?p=11986041&postcount=192 how do I install it, same way I did to install Dexter's or gotta flash for stock and redo the whole process?
1.1- I NEED TO create that ext3 partition or is it optional?
1.2- Is this ROM the same as Dexter's 1.3 but with the new theme?
2- What's yours phone avarage temperature? Even with stock ROM I think my XT is a too hot near the camera, it says 41°C Avarage, is it normal?
Thanks in advice!
You download the KPs nandroid file & unzip it then copy the xthoneycomb folder to the /nandroid/openrecovery/ folder on yours sdcard & then just boot into OpenRecovery & nandroid restore just like the installation of Dexters Froyo, no need to flash back to stock & the ext3 patition is optional it will use it if its there but its not necessary. Khalpowers themes throw in a few other tweaks but are generally built off Dexter's Froyo.
3rdstring said:
You download the KPs nandroid file & unzip it then copy the xthoneycomb folder to the /nandroid/openrecovery/ folder on yours sdcard & then just boot into OpenRecovery & nandroid restore just like the installation of Dexters Froyo, no need to flash back to stock & the ext3 patition is optional it will use it if its there but its not necessary. Khalpowers themes throw in a few other tweaks but are generally built off Dexter's Froyo.
Click to expand...
Click to collapse
Thanks again man, I feel safer now to do it, got this phone there isn't even a day and I'm already flashing it, so I'm a bit scared of doing any mistake and Bricking it..
And a final question, Quadrant and Milestone Overlock show CPU defaut Clock as 550 Mhz, shouldn't it be 720?
Edit:
Just flashed it: OMG this is so beatiful ! The collors match perfectly with XT720's collor (Graffite front/blue rear) ! And the way that the pages/tabs pop in on the screen is so cool ! It's a completly new phone, much better. Now is just install my apps and have fun! =D the only thing that is worrying me is that fact that the phone is very hot, even at 550 Mhz.. dunno if it's the XT720 normal temperature, but I don't think so.
I have the questions regarding the installation of the ROM Dexter,
1. ext3 will need to take before making the change in ROM, or that I can do next?
2. To work App2Sd is necessary to partition the SD?
Thanks for the help
1) you can do that after you flash the Froyo
2) you don't need to if you plan to use Froyo's Apps 2 SD
but you need to if you want to use Link2SD
Tavinsky said:
I have the questions regarding the installation of the ROM Dexter,
1. ext3 will need to take before making the change in ROM, or that I can do next?
2. To work App2Sd is necessary to partition the SD?
Thanks for the help
Click to expand...
Click to collapse
@ Lezherus
Check here for info about Milestone OC settings (I run 1GHZ @ 60vsel, governed with SetCPU).
@ Tavinsky
It is my understanding that the check for an ext3 partition happens at boot, so you I think you could "add" this feature later & yes you will have to partition your sdcard to take advantage of the apps2ext feature. Note that Froyo native apps2sd which can copy compatible apps to a hidden folder on the FAT32 works without any re-partitioning.
HTH
Thanks guys, I'm about to change the ROM, their responses are very helpful.
Greetings!
3rdstring said:
@ Lezherus
Check here for info about Milestone OC settings (I run 1GHZ @ 60vsel, governed with SetCPU).
@ Tavinsky
It is my understanding that the check for an ext3 partition happens at boot, so you I think you could "add" this feature later & yes you will have to partition your sdcard to take advantage of the apps2ext feature. Note that Froyo native apps2sd which can copy compatible apps to a hidden folder on the FAT32 works without any re-partitioning.
HTH
Click to expand...
Click to collapse
I know, that wasn't my point.. I mean, thats like my XT's processor orginal clock is 550Mhz, even at 2.1 stock it was 550 Mhz, but isn't the stock 720Mhz? or there are differents types of XT720? And thats totally weird, but at 550Mhz my phone was a firebar ( 41°C at no use and 45 at common use ), I overclocked it to 1000Mhz and it's normal now lol (38°C).
BTW, someone know how to disable the new voice mail notification on status bar? It's stucked there and I can't remove it.. I've already read all my voice mails, tried everything and it still there =(
It should just automatically disappear. Delete everything from VM?
Accophox said:
It should just automatically disappear. Delete everything from VM?
Click to expand...
Click to collapse
Yes, I've read all my VMs, deleted them all.. and the notification still there.. I've read a bit and some people with the same problem solved it by calling the carrier, coz that notification come from them.. I will try later on..
Wantedrom 1.3 screen rotate/youtube upload
So I've tried all the variation from Dexter's first 2.2 rom and have stopped with the latest Wanted Rom1.3
Two things I'm not liking...
1: my screen will not rotate if I am using the keyboard for a text message and would like the larger button layout.
2: I no longer have the option of uploading a video from my phone directly to Youtube. Youtube downloads were only done using stock2.1 so maybe I missed that this was missing from the roms I've previously tried as well.
anybody have any thoughts?
Wanted 1.3 - no screen autorotate
No rotate for anything.
No rotate for anything.
Click to expand...
Click to collapse
should not be like that, you set the option to rotate screen?
Tavinsky said:
should not be like that, you set the option to rotate screen?
Click to expand...
Click to collapse
Of course, it's "on". I even reflashed this ROM again and wiped all cache and set to factoty settings before it. Problem stays the same - no autorotate.
Tried Wanted ROM 1.2 and Dexter 1.3, everything works there. The problem seems to be in this Wanted ROM version.
no real wheel...
Sent from my Milestone XT720 using XDA App
Autorotate
The screen will rotate for games and applications that require a landscape view instead of portrait but not for anything where it is an option.
I backtracked a little and set my phone to wantedrom 1.2. I didn't even do a factory reset as everyone is always insisting is necessary. Autorotate fixed, all my applications stayed loaded and functional as before.
Overclocked at 1200 MHz , 80vsel and the phone is screaming fast.
After I typed this, I checked the wanted forum and found his solution to the sensor issue...
http://forum.xda-developers.com/showthread.php?t=961731&page=16
I have been spending many hours, days, and weeks trying to learn as much as possible about modding my android....but I am still a little lost.
Details:
Motorola Motoroi XT720 (I am in Korea)
S/W version: STSKT_N_79.33.50R
Android Version: 2.2.1 (Just upgraded the other day from Motorola's website)
Kernel Version: 2.6.29-omap1
Also, I am rooted.
I am not sure if I am unable to mod mine to the extent that others can (due to mine being the Korean version), or if it just the fact that I am still learning and not completely "Android Savy" yet. But if I could get some assistance, it would be greatly appreciated.
I'd hate to say it, cause I can be pretty smart, but if it could be be broken down "Barney Style" for me, that would be great.
I would like to change up the phone to have a much more powerful machine. Without lag, runs faster/smoother (overclock), change the appearance (black status bar, etc), and pretty much anything else possible.
I see some ROMs that say they are for "Dexter's 2.2", etc...would those work for me even though I have the "legit" 2.2 from Motorola?
Any and all help would be greatly appreciated!!
One problem you will encounter is that the Motoroi has a much smaller system partition than what we use on Dexter-derived XT720 ROMs. So I don't think you will be able to copy on Dexter's ROM (or the modified Dexter ROMs). That said, I don't think you need it:
If you haven't already you should see if you can get Open Recovery or Androidiani Recovery (better) installed so that you can backup and restore when things don't work.
For overclocking, try Milestone Overclock from the market. I think it was updated recently to support the Motoroi kernel, but I could be wrong. If it doesn't work, you just need to make an init.d script to load the kernel module with the correct offsets (I can give more details if needed).
For theming, see if Metamorph (in market) works. There's a gingerbread theme http://forum.xda-developers.com/showthread.php?t=955698 that you can try to see if the morphs we're using are compatible.
Other things to try are old school app2sd if you have low internal memory (Motoroi is partitioned for more internal memory than the Dexter ROMs).
Mioze7Ae said:
If you haven't already you should see if you can get Open Recovery or Androidiani Recovery (better) installed so that you can backup and restore when things don't work.
Click to expand...
Click to collapse
I have Root Manager and have backed up with that...Will that work just fine?
For overclocking, try Milestone Overclock from the market. I think it was updated recently to support the Motoroi kernel, but I could be wrong. If it doesn't work, you just need to make an init.d script to load the kernel module with the correct offsets (I can give more details if needed).
Click to expand...
Click to collapse
I have tried the milestone overclock and it wouldnt work for me. Everytime I tried to "Load Module", it would just say "Load Failed".
If you could further explain what an init.d script is, and how to load it...that would be great.
For theming, see if Metamorph (in market) works. There's a gingerbread theme http://forum.xda-developers.com/showthread.php?t=955698 that you can try to see if the morphs we're using are compatible.
Click to expand...
Click to collapse
I'll be sure to check that you, how do you recommend applying the themes? I've seen numerous ways of doing it. Metamorph app?
Other things to try are old school app2sd if you have low internal memory (Motoroi is partitioned for more internal memory than the Dexter ROMs).
Click to expand...
Click to collapse
After upgrading to 2.2, I am now able to move apps to my SD Card...does that work just fine, or would app2sd offer more for me?
-eXpo- said:
I have Root Manager and have backed up with that...Will that work just fine?
Click to expand...
Click to collapse
I'm not sure Root Manager can help you if you get stuck in a bootloop. The recoveries will let you save bit-perfect images of the phone that can be restored (nandroid).
I have tried the milestone overclock and it wouldnt work for me. Everytime I tried to "Load Module", it would just say "Load Failed".
If you could further explain what an init.d script is, and how to load it...that would be great.
Click to expand...
Click to collapse
Ok, you can create boot scripts, but this could be pretty involved and take a lot of time. I don't think Motorola's stock ROMs run /system/etc/init.d directory scripts so it would involve creating a boot hijack. The easiest thing may be to file a bug report so that Milestone Overclock can be updated for the Motoroi 2.2 kernel. This would be the best solution. Run:
cat /proc/kallsyms > /sdcard/kallsyms.txt
and post the kallsyms.txt and your kernel version (i.e. something like 2.6.32.9 [email protected]#1, but from your phone) to:
http://code.google.com/p/milestone-overclock/issues/list
I'll be sure to check that you, how do you recommend applying the themes? I've seen numerous ways of doing it. Metamorph app?
Click to expand...
Click to collapse
Metamorph is an app. It's pretty easy when it works.
After upgrading to 2.2, I am now able to move apps to my SD Card...does that work just fine, or would app2sd offer more for me?
Click to expand...
Click to collapse
Yeah, that's completely fine. Don't bother if you don't need it.
I used the ROM from here. (LG Optimus T (P509): January 8: Build 7/Final)
I have no Google Play store icon anywhere. I see the Google Play process running in the background.
but have no way to get it to show up. This on a fresh ROM, all User data, Cache, and all that cleared.
Any help on this would be nice.
Would of asked on that post where I got the ROM. but I don't have the patience to or any thoughts about other post to make to meet the requirements to even post there.
Tried without flashing the Google Apps and with the google apps they list there.
Flashing Google Apps just crashes things like the browser. it wont even open.
Not flashing Google Apps I can use the browser just fine. but I still see "Google Play Services" Running. So that tells me google play is installed.
So don't have to flash it. but cant open it even if i did or not. no Icon anywhere no matter what I try. I been wanting to use CM10. but this issue keeps me going back to CM7.
Thanks in advance to the person with the answer.
TroyFoxxin said:
I used the ROM from here. (LG Optimus T (P509): January 8: Build 7/Final)
I have no Google Play store icon anywhere. I see the Google Play process running in the background.
but have no way to get it to show up. This on a fresh ROM, all User data, Cache, and all that cleared.
Any help on this would be nice.
Would of asked on that post where I got the ROM. but I don't have the patience to or any thoughts about other post to make to meet the requirements to even post there.
Tried without flashing the Google Apps and with the google apps they list there.
Flashing Google Apps just crashes things like the browser. it wont even open.
Not flashing Google Apps I can use the browser just fine. but I still see "Google Play Services" Running. So that tells me google play is installed.
So don't have to flash it. but cant open it even if i did or not. no Icon anywhere no matter what I try. I been wanting to use CM10. but this issue keeps me going back to CM7.
Thanks in advance to the person with the answer.
Click to expand...
Click to collapse
Are you sure you are using the right GApps package? That's Rasheds ROM you're referring to using. Build 7 is Android 4.1.2. Check this link here. And some of the problems you may be experiencing could be due to a faulty installation because of limited system space. You may want to review the LG Optimus One FAQ too.
shinobisoft said:
Are you sure you are using the right GApps package? That's Rasheds ROM you're referring to using. Build 7 is Android 4.1.2. Check this link here. And some of the problems you may be experiencing could be due to a faulty installation because of limited system space. You may want to review the LG Optimus One FAQ too.
Click to expand...
Click to collapse
There is more then enough internal space. (150MB Free after Gapps Flashed).
I tried again with the Gapps for 4.1.2. At the time my post I re flashed the ROM but left it out. I didn't flash it.
When I tried again. I got the Updating Android. but still no Play Store Icon. However it did not break my home or other buttons.
and browser still working. but again. no Play Store icon.
I checked the FAQ. Currently i see nothing there to give hints. I got more then enough free space. I've flashed ROMs on this phone dozens of times so I know the whole wiping of cache and data and all that between each ROM.
TroyFoxxin said:
There is more then enough internal space. (150MB Free after Gapps Flashed).
I tried again with the Gapps for 4.1.2. At the time my post I re flashed the ROM but left it out. I didn't flash it.
When I tried again. I got the Updating Android. but still no Play Store Icon. However it did not break my home or other buttons.
and browser still working. but again. no Play Store icon.
I checked the FAQ. Currently i see nothing there to give hints. I got more then enough free space. I've flashed ROMs on this phone dozens of times so I know the whole wiping of cache and data and all that between each ROM.
Click to expand...
Click to collapse
You have to trim the Rom, there's not enough SYSTEM space for the Rom and Gapps..this has been discussed time and time again on rashed thread(cm10)..There's a tool ( Oone Rom editor that will help you do this) This is why you have the bugs that your facing.
3ncrypt3d_Droid said:
You have to trim the Rom, there's not enough SYSTEM space for the Rom and Gapps..this has been discussed time and time again on rashed thread(cm10)..There's a tool ( Oone Rom editor that will help you do this) This is why you have the bugs that your facing.
Click to expand...
Click to collapse
I used that program already. looking at all that it would only show.
the math dont even come to half of what the phone memory is.
TroyFoxxin said:
I used that program already. looking at all that it would only show.
the math dont even come to half of what the phone memory is.
Click to expand...
Click to collapse
The system partition has nothing to do with the devices memory. These devices have a 190 MB system partition, this is where Android gets installed. What you are referring to is the user data partition which is 200 MB, while the device has 415 MB+- RAM ( memory ). Unless you are using Android 4.2.2, the only way to see how much space is on the system partition is with a third party app, with ADB, or with a Terminal Emulator app on the device. The math isn't adding up because you don't understand it, that's why I pointed you to the FAQ thread.
I wrote OOne ROM Editor. I haven't put hundreds, yes hundreds, of hours in to it's development just for general pleasure. It was written for a specific purpose, to trim ICS and newer ROMs for devices with small or limited system partitions.
shinobisoft said:
The system partition has nothing to do with the devices memory. These devices have a 190 MB system partition, this is where Android gets installed. What you are referring to is the user data partition which is 200 MB, while the device has 415 MB+- RAM ( memory ). Unless you are using Android 4.2.2, the only way to see how much space is on the system partition is with a third party app, with ADB, or with a Terminal Emulator app on the device. The math isn't adding up because you don't understand it, that's why I pointed you to the FAQ thread.
I wrote OOne ROM Editor. I haven't put hundreds, yes hundreds, of hours in to it's development just for general pleasure. It was written for a specific purpose, to trim ICS and newer ROMs for devices with small or limited system partitions.
Click to expand...
Click to collapse
I dont know what to try to trim with that program. i dont know what half them apps do.
Like Exchange2.apk. I don't know what that is. Which are some of the key things i can trim?
Also, Telling me how many hours you put into a program and that i dont understand something not going to be on my good side. So i missed something, big deal. I just got off a anxiety attack. and i was needing was a simple answer. doing a search for "LG P509 No Playstore Icon" was getting me no where and i didnt want to have to search page by page of the 487 pages of the ROMs post to find clues.
TroyFoxxin said:
I dont know what to try to trim with that program. i dont know what half them apps do.
Like Exchange2.apk. I don't know what that is. Which are some of the key things i can trim?
Click to expand...
Click to collapse
The help docs in OOne ROM Editor's thread list some of the known files that can be removed from and or moved around, ie; converted to user app, in the ROM.
shinobisoft said:
The help docs in OOne ROM Editor's thread list some of the known files that can be removed from and or moved around, ie; converted to user app, in the ROM.
Click to expand...
Click to collapse
just never mind. i dont need the stress right now, ill just stay with CM7.
Every time i try to Build the ROM and put it on the phone CWM just says its bad.
TroyFoxxin said:
just never mind. i dont need the stress right now, ill just stay with CM7.
Every time i try to Build the ROM and put it on the phone CWM just says its bad.
Click to expand...
Click to collapse
Are you getting an "assert() failed" message? If you are using CWM 5.0.2.7 Touch, it will only allow you to install P500 ROMs. OOne ROM Editor has the ability to remove the "assert()" statement from the ROM's updater-script to prevent that particular error from happening. Before building the ROM, go to the Tools->Build submenu and select the Build Options command. Check the checkbox for "Remove updater-script 'assert()' statement". Then build the ROM.
And stress... You call editing a ROM stress? Try writing the code for OOne ROM Editor Or better yet, play with live electricity :silly: - oh wait I do that already since I am an electrician... DOn't get frustrated by it. Sit back relax and soak in some of the knowledge around here.
shinobisoft said:
Are you getting an "assert() failed" message? If you are using CWM 5.0.2.7 Touch, it will only allow you to install P500 ROMs. OOne ROM Editor has the ability to remove the "assert()" statement from the ROM's updater-script to prevent that particular error from happening. Before building the ROM, go to the Tools->Build submenu and select the Build Options command. Check the checkbox for "Remove updater-script 'assert()' statement". Then build the ROM.
And stress... You call editing a ROM stress? Try writing the code for OOne ROM Editor Or better yet, play with live electricity :silly: - oh wait I do that already since I am an electrician... DOn't get frustrated by it. Sit back relax and soak in some of the knowledge around here.
Click to expand...
Click to collapse
Again bad, day. had a Anxiety attack. haven't slept. I havent played with Android as often as other things. I am also a Electronic person. Soldering Caps and so on on motherboards all the time. So please dont talk like that to people you dont know. they may have plenty of knowledge. but maybe having whats called a short fuse kinda day.
Also I did do "Remove updater-script 'assert()' statement". And i get no error from OOne ROM Editor it was in CWM it would just say it was bad, or say nothing at it would just restart CWM. Ill try again when Im better. Right now my phone has CWM 5.0.2.0, So ill change that as well when i try again.
but right im turning in for the night.
TroyFoxxin said:
Again bad, day. had a Anxiety attack. haven't slept. I havent played with Android as often as other things. I am also a Electronic person. Soldering Caps and so on on motherboards all the time. So please dont talk like that to people you dont know. they may have plenty of knowledge. but maybe having whats called a short fuse kinda day.
Also I did do "Remove updater-script 'assert()' statement". And i get no error from OOne ROM Editor it was in CWM it would just say it was bad, or say nothing at it would just restart CWM. Ill try again when Im better. Right now my phone has CWM 5.0.2.0, So ill change that as well when i try again.
but right im turning in for the night.
Click to expand...
Click to collapse
Sorry you're having a bad day. Rest assured, if I was talking down to you, there wouldn't be any smilies. I was just expressing that you weren't the only one out there with stress in their life, and some of us have loads of it. On that note, I'm not one of the many teenagers around here. So I'm not talking down to you, but out of experience. My teenage years were gone 23 years ago. Apparently it was take outta context, Sorry.
I think the issue I mentioned for CWM 5.0.2.7 is a shared issue with CWM 5.0.2.0, but I can't say for sure as I don't recall ever using CWM 5.0.2.0. I wasn't suggesting changing to the CWM I mentioned, was asking if that was the one you were/are using, which you've now stated you aren't. There error I was referring to would have been from CWM after flashing or trying to flash a ROM.
shinobisoft said:
Sorry you're having a bad day. Rest assured, if I was talking down to you, there wouldn't be any smilies. I was just expressing that you weren't the only one out there with stress in their life, and some of us have loads of it. On that note, I'm not one of the many teenagers around here. So I'm not talking down to you, but out of experience. My teenage years were gone 23 years ago. Apparently it was take outta context, Sorry.
I think the issue I mentioned for CWM 5.0.2.7 is a shared issue with CWM 5.0.2.0, but I can't say for sure as I don't recall ever using CWM 5.0.2.0. I wasn't suggesting changing to the CWM I mentioned, was asking if that was the one you were/are using, which you've now stated you aren't. There error I was referring to would have been from CWM after flashing or trying to flash a ROM.
Click to expand...
Click to collapse
Can that program add apps? If so or not. maybe I can edit the zip directly. but is it possible to port the old music player in Gingerbread to JB. I don't like Apollo. or would it just be better to remove Apollo and find something I like in Play store when i make this work?
And should i try to use CWM 5.0.2.7 instead, and try again?
EDIT: Says I have the latest according to this.
EDIT 2: just ROM Manger being a butt. going to the site directly. I see CWM 5.0.2.7 as the latest.
TroyFoxxin said:
Can that program add apps? If so or not. maybe I can edit the zip directly. but is it possible to port the old music player in Gingerbread to JB. I don't like Apollo. or would it just be better to remove Apollo and find something I like in Play store when i make this work?
And should i try to use CWM 5.0.2.7 instead, and try again?
EDIT: Says I have the latest according to this.
EDIT 2: just ROM Manger being a butt. going to the site directly. I see CWM 5.0.2.7 as the latest.
Click to expand...
Click to collapse
Yes apps can be added, but only as User Apps. Select "User Apps" in the treeview on the left. Then right click on the listview on the right and select the "Add apps" command item. A file dialog will appear. Multiple file selection is allowed.
You can remove Apollo. I prefer Google Play Music myself.
For your recovery. CWM 5.0.2.7 will only allow installing P500 ROMs. I do prefer the touch version of CWM, and since P509 is identical to P500, it's really not an issue other than baseband which is solved with a flashable patch. I really cannot recommend a recovery as we all have different likes/dislikes/usage patterns. I would recommend not using ROM Manager to install a recovery. It's been known to be faulty with our devices. Theres always ADB and fastboot or another one of my tools, Android Flash Recovery. There are several other apps around XDA that can do this also.
shinobisoft said:
Yes apps can be added, but only as User Apps. Select "User Apps" in the treeview on the left. Then right click on the listview on the right and select the "Add apps" command item. A file dialog will appear. Multiple file selection is allowed.
You can remove Apollo. I prefer Google Play Music myself.
For your recovery. CWM 5.0.2.7 will only allow installing P500 ROMs. I do prefer the touch version of CWM, and since P509 is identical to P500, it's really not an issue other than baseband which is solved with a flashable patch. I really cannot recommend a recovery as we all have different likes/dislikes/usage patterns. I would recommend not using ROM Manager to install a recovery. It's been known to be faulty with our devices. Theres always ADB and fastboot or another one of my tools, Android Flash Recovery. There are several other apps around XDA that can do this also.
Click to expand...
Click to collapse
Ill just leave it be then. Its always worked for me. if there was a problem it was with the ROM.
I haven't tried Google Play music before. but is it possible to port the music player from Gingerbread to JB?
but I'm getting the jiffs of that program. I just need to play with it. some things I converted to User apps never loaded at all.
So I need to play with what I can put in User data that will still work. but none the less i been getting the builds to install.
And even show Play Store again.
Just need to mess with what works and dont in User data.
-Edit-
I tried to Make LatinIME Smaller and convert it to Userdata in the build options but every build has no keyboard support.
TroyFoxxin said:
Ill just leave it be then. Its always worked for me. if there was a problem it was with the ROM.
I haven't tried Google Play music before. but is it possible to port the music player from Gingerbread to JB?
but I'm getting the jiffs of that program. I just need to play with it. some things I converted to User apps never loaded at all.
So I need to play with what I can put in User data that will still work. but none the less i been getting the builds to install.
And even show Play Store again.
Just need to mess with what works and dont in User data.
-Edit-
I tried to Make LatinIME Smaller and convert it to Userdata in the build options but every build has no keyboard support.
Click to expand...
Click to collapse
Is there anyway you can post the updater-scipt from one of the builds you've made with OOne ROM Editor where you've modified the LatinIME.apk and specified to install as a User App? The updater-script is located in the /META-INF/com/google/android folder in the output/build ROM.
One thing to note tho, build options are reset after every build.
shinobisoft said:
Is there anyway you can post the updater-scipt from one of the builds you've made with OOne ROM Editor where you've modified the LatinIME.apk and specified to install as a User App? The updater-script is located in the /META-INF/com/google/android folder in the output/build ROM.
One thing to note tho, build options are reset after every build.
Click to expand...
Click to collapse
I noticed that it resets everytime. so i been ontop of that. I check both boxes in the build options before I build them.
I did read also not to delete LatinME.apk. and use the editor. But i know the LatinME is a nice chunk of Memory.
So to make it smaller and usable in User apps is plus to make the important things I need working.
-Edit-
I haven't been saving the bad builds. that attachment was for a new build I haven't tried yet.
and I just did. now keyboard working. But I think that build I didn't tell it to put Latin in User apps that time.
But I did use the editor. So I don't know.
TroyFoxxin said:
I noticed that it resets everytime. so i been ontop of that. I check both boxes in the build options before I build them.
I did read also not to delete LatinME.apk. and use the editor. But i know the LatinME is a nice chunk of Memory.
So to make it smaller and usable in User apps is plus to make the important things I need working.
-Edit-
I haven't been saving the bad builds. that attachment was for a new build I haven't tried yet.
and I just did. now keyboard working. But I think that build I didn't tell it to put Latin in User apps that time.
But I did use the editor. So I don't know.
Click to expand...
Click to collapse
I can't tell what you installed as user apps from the updater-script, but there were apps installed to the user ( data ) partition. And the assert() statement is missing from the script, so I know that option was checked in the Build Options.
The reason I say not to manually move it is because the LatinIME Keyboard Editor should be used to edit it's dictionaries. Once you press the "Apply" button in the LatinIME Keyboard Editor, it removes the LatinIME.apk from System Apps and actually puts it in the apps Recycle Bin. I use the list of files in the Recycle Bin as a filter of files not to include when building the ROM. LatinIME Keyboard Editor also looks in the Recycle Bin for the LatinIME.apk if it can't find it in System Apps but it assumes that it's deleted so it won't do anything.
I am actually working on OOne ROM Editor right now. So you can be on the lookout for an update
shinobisoft said:
I can't tell what you installed as user apps from the updater-script, but there were apps installed to the user ( data ) partition. And the assert() statement is missing from the script, so I know that option was checked in the Build Options.
The reason I say not to manually move it is because the LatinIME Keyboard Editor should be used to edit it's dictionaries. Once you press the "Apply" button in the LatinIME Keyboard Editor, it removes the LatinIME.apk from System Apps and actually puts it in the apps Recycle Bin. I use the list of files in the Recycle Bin as a filter of files not to include when building the ROM. LatinIME Keyboard Editor also looks in the Recycle Bin for the LatinIME.apk if it can't find it in System Apps but it assumes that it's deleted so it won't do anything.
I am actually working on OOne ROM Editor right now. So you can be on the lookout for an update
Click to expand...
Click to collapse
Well I got everything to work. Keyboard, Play Store, etc. But not sure ill stick with trying to put JB on the phone.
Its really slow. Unless more free space on the system partition would allow it to run faster.
Would your OOne ROOM Editor work on Any rom Like a CM7 Rom? or just JB ones? if not would you consider support for other roms?
I haven't tried, but figure I would ask.
TroyFoxxin said:
Well I got everything to work. Keyboard, Play Store, etc. But not sure ill stick with trying to put JB on the phone.
Its really slow. Unless more free space on the system partition would allow it to run faster.
Would your OOne ROOM Editor work on Any rom Like a CM7 Rom? or just JB ones? if not would you consider support for other roms?
I haven't tried, but figure I would ask.
Click to expand...
Click to collapse
OOne ROM Editor is just for ICS and JB ROMs. It's really not needed for Android versions prior to 4.0.