Related
[ROM][32A RADIO 6.35]Eclair w/ Nexus1's 3D gallery CAM & most things are working well
this ROM is for Sapphire 32A SPL 1.76.2007 and latest Radio 6.35.07.29.
pure AOSP build, google bits and gallery are added. (make sure you think you have the rights for using the apps from google, i just make some copy for you)
thx: Cursordroid, Enomother, Cyanogen, RA, jnwhiteh, ChainsDD, sober (who have full of courage for testing my first kernel ) , and more...
what's new: less crash, more stable. new gallery app which use hardware accel. a new step to full working with our new radio.
the update.zip, just push it into ur sdcard then apply it from recovery: http://www.4shared.com/file/202007372/5352e8b4/my2x.html
mirrors:
http://hotfile.com/dl/24995574/2b6c9d7/sanpei_eclair32a.zip.html , by asero, thanks
http://www.megaupload.com/?d=5TH7FNC0 , by akai21, thanks
http://hoegsberg.net/fileshare/Sanpei Eclair 2.1/ , by Eukanaba, thanks
if you are a 32A user with old radio, and you want a upgrade or try this ROM, follow Cursordroid's instruction to Update your 32A Magic to 6.35.07.29 Radio and 1.76.2007 SPL
working (update: all confirmed by me or other users):
camera
gps
wifi
mobile data
sensor
lights
gps
bluetooth
openGL
Gallery3D
googlebits
working but leaving some questions open:
playback (will print error message in log, not tested with many format)
not working properly:
camcorder (only preview working)
I would not say "it is very fast", but I feel it fast enough. and if you do not care about the multi-media things, i think this build seems not bad.
(for the multi-media things, they are mostly caused by media libs in AOSP, which google have not done yet. (but i cannot understand why nexus-one can have a stable version !!!) it is not all the HTC/Qualcomm's fault, Google didn't do their job very well too)
if there are something I missed, or I made some mistake, don't be sulkiness plz. i will fix them with you. let us make it better and make more 32A user switching to new Radio, with more users, we can do better and more quickly.
file/things includes:
AOSP master, I keep it at the API version 5, because things with API 7 for other devices (except nexus1) are not stable, i don't want to pretend that we have a nexus1, and make things unstable.
su and superusers from ChainsDD.
kernel which i modified from msm-kernel-2.6.29.
libhtc_ril.so, omx libs are from a leaked official 2.x ROM. camera libs, libgps.so from another one. (thanks the man who provided them)
libhtc_acoustic.so and some miscs files from official 1.5 ROM. akmd too, but akmd from 1.6 ROM have newer version and i think it will works too.
google bits are come from different sources too:
Gallery3D/google framework parts from nexusone dump, i think Enomther deodexed them, thank you and I LOVE YOU.
Other google's things are versions used everywhere, and here are my thanks to the one dumped them --> m(_ _)m.
cyanogen's patch which is directed towards infinite sync. it may be a temporary workaround, when google do things right, i will remove it.
.......
more: lock screen and wallpaper is the eclair's initial one as AOSP source released with them. if you want other lock screen, customize it yourself, and tell me how ^^, I'm really not a good cooker .
known issues and workaround:
1. camcorder can not record, but it didn't crash anything as previous one (with my kernel, from jnwhiteh) would crash some.
2. video playback has many errors the video can be played though. just reported by logcat, and no more thing will happen in my tests.
3. if you stay in the Gallery3D UI, and the phone sleeps later, when it wake up, the Gallery3D lost hardware acceleration. you can quit and enter this app again, it will be fine.
4. first boot with google bits may not go without a hitch. you can remove all google apps in the zip (you must resign it) and push them later.if you boot with googlebits:
you will see a dialog let you choose the default behavior, select SetupWizard here. if you select another, you can not use internet during the first boot, it will say "no connection", though we are connected.
the SetupWizard will start twice, the second one is for asking you to sign in a google account, you can just press menu to quit.
and there are many lags in first boot, maybe black screen (can not light, you can "adb reboot" it) or some crash (i have met once for each and I flash it serveral times) if you operate too fast.
after second boot, it will works fine. it seems if we give the phone more time to do many initialize jobs, it will work happily even in first run.
5. with superuser, if you select deny, the app which needed the permissions may be force closed. it is a bug in su sources i used which is not belong to me and i have no time to look and fix it yet.
update:
6. when wake up the phone, screen turned on, but backlight of screen not. if you can see image, just go to setting and set brightness, then the light will open. need more reports (like situation/logcat/dmesg, etc.) to locate the problem. i encountered this problem once.
7. "died in sleep", this problem has been encountered by others, personally, i met it once during first run, after a reboot I never met it again. but I don't think this problem just appears during first run. instead, i think the situation of first run is more closed to the condition triggering it.
I think there must be more problems, let us find them together, and fix them by our hands.
update: after some search I found that some softwares (like nettraffic) will cause more "died in sleep" in some ROM/kernel/Radio combination. and many kinds of "died in sleep" can be avoid with some tweaks, but i don't know if they are same problems as ours, and i can not get what this tweaks are (or why, how..) from anywhere yet.
i am waiting for more details to fix 6 & 7. I will be grateful if someone can provide some info about similar problems, since I had seen these problems in some other ROM/kernel/Radio combination.
and guys who encountered these problems, could you provide more details plz? something like: occurred during first run/other, with situation XX (mobile/wifi/software X running, etc) which you think it caused the problem occurred more often. if you can reproduce it, we will get very closed to fixing them.
great job!
Another ROM using the latest SPL/Radio... great!
Downloading now.. will try flashing later...
Nice work sanpei!
Great job. I will try it immediatly.
Excellent, nice to see some other developers working on this radio/SPL version as well!
I will definitely be trying this out today!
Awesome will try when I get home from work.
Would it be possible to implement the Nexus apps-menu in a later build?
bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!
asero said:
bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!
Click to expand...
Click to collapse
I will look into this, but I cannot locate this problem quickly, since I just met it once during a first boot, and it never appears again.
is it like the situation "die in sleep" in some build which are based on CyanogenMod? (when i was using old radio)
can you reproduce the problem and description the operations? thx.
Eskibo said:
Awesome will try when I get home from work.
Would it be possible to implement the Nexus apps-menu in a later build?
Click to expand...
Click to collapse
maybe or maybe not is there anybody who have the right skills could try it for us? (i have some other things to do) i will join later.
Newb questions
Hi Guys,
Sorry for the lame newb questions. I just want to verify this prior to trying this ROM.
I'm currently using CursorSense 1.0.1 - which is my every day ROM (great functionality, fast, does everything I need)
I'm really interested in trying out Android 2.1 - and seeing as this uses the same SPL / Radio - it means I should be able to just wipe and flash this one. HOwever seeing as I just want to take a peek and play around with it, I don't want to screw up everything on my phone toooo badly lol.
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten
asero said:
bug report:
The screen remains black (can't see anything) after sleeping even if I press any of the buttons. I just removed the battery then reboot.
Aside from that, it's quite fast and responsive. The transitions are nice too. Keep it up dude!
Click to expand...
Click to collapse
I encountered this issue too. I also encountered this issue once with aosp-2.0.1-jnwhiteh-r6.
Gritten said:
Hi Guys,
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten
Click to expand...
Click to collapse
Yes.. backup, wipe, flash, try, wipe, restore.. I even think that last wipe isn't even necessary, but it doesn't harm either. A Nandroid restore restores your phone exactly as you left it (incl. your call log, SMS, apps, etc.)
It could be that some new folders/files are created on your SD card (if required by Eclair apps), but since they are not used by your previous rom it won't be a problem (unless you don't want to keep those unused folders and files on your SD card).
If you are not sure, or don't want to keep the extra folders/files, you can always make a backup of your SD card on a USB or PC prior to trying the rom.
Have fun! ;-)
Gritten said:
Hi Guys,
Sorry for the lame newb questions. I just want to verify this prior to trying this ROM.
I'm currently using CursorSense 1.0.1 - which is my every day ROM (great functionality, fast, does everything I need)
I'm really interested in trying out Android 2.1 - and seeing as this uses the same SPL / Radio - it means I should be able to just wipe and flash this one. HOwever seeing as I just want to take a peek and play around with it, I don't want to screw up everything on my phone toooo badly lol.
If I do a nand backup - wipe and flash this new ROM, when I'm done, can I do a wipe, then reflash the nandroid backup and everything will go back to the way I have it setup now?
Also will anything get screwed up on my SD card leaving it as it is flopping from one ROM to the other and then back (it's non partitioned, and loaded with misc folders created from my apps)
Thanks!
Gritten
Click to expand...
Click to collapse
Yes. You can restore from nandroid backup and everything will go back. I often switch between CursorSense 0.4 and sanpei's rom several times a day.
so can anyone answer if this is a good everyday rom? or equivelant to cursor sense?
shael said:
so can anyone answer if this is a good everyday rom? or equivelant to cursor sense?
Click to expand...
Click to collapse
The ROM is well done. It's responsive (no lag from my playing) even the 3d gallery ran very well.
I didn't use it too long for everyday items as I'm a Sense fan, however I find that standard plain Android is pretty empty when I don't have my sense stuff on top lol.
Definately play around with it if you're interested.
sober said:
I encountered this issue too. I also encountered this issue once with aosp-2.0.1-jnwhiteh-r6.
Click to expand...
Click to collapse
Me too!
Awesome ROM.
Keep UP dude!
Been testing it for a few hours. So far not a single FC and i can confirm that BT works just fine, also OBEX with Bluetooth File Transfer by medieval software.
SMS and emails send and get received just fine.
Tested the GPS in both google maps and the GPS status app to check efficiency, and so far everything works just fine.
The gallery is really sexy, now we just need to get the Nexus1 apps-menu implemented .
Actually there are three other things i'd like implemented also:
Animated desktop
Wireless tether
Google Nav
What do people think about that?
Eskibo said:
Been testing it for a few hours. So far not a single FC and i can confirm that BT works just fine, also OBEX with Bluetooth File Transfer by medieval software.
SMS and emails send and get received just fine.
The gallery is really sexy, now we just need to get the Nexus1 apps-menu implemented .
Actually there are three other things i'd like implemented also:
Animated desktop
Wireless tether
Google Nav
What do people think about that?
Click to expand...
Click to collapse
Will be even better with u suggestion and Sense!
fabioccoelho said:
Will be even better with u suggestion and Sense!
Click to expand...
Click to collapse
I wish I had some idea of how to do those things, then I would surely try help doing it.
Not sure if this is the place to get an answer, but I have a big problem. HelixLauncher has locked my Droid Getting a pop-up message: "Helixlauncher has stopped unexpectedly, please try again" with a small command window that says "Force Close". Touching Force Close just brings back the message again and no other commands are possible. Tried removing battery, but same issue repeats. Phone is currently unusable until I find a solution. Please help.
You could use adb to remove helixlauncher. That is, if you didn't remove the stock launcher.
adb remount
adb shell
rm /system/app/ whatever the name of the helix launcher app is
Click to expand...
Click to collapse
sounds like someone should have nanded ..... if whats posted above doesn't work, re-flash your rom.....take it as a lesson, nanding is your best friend
Your, ah, Droid? Not that I think you should be stoned and chased out for posting about something non-N1, but...
That aside, were you using just plain HelixLauncher or HelixLauncher2? The latter was developed for the N1 and, as I understand, doesn't play nice with Droids.
N1 in same trouble
Although tech savvy, still new to Android & N1.
Thought I needed HelixLauncher and installed it on to my N1 w/ 2.1 u1. Was working ok, but I decided to drop screen size to 1.
It's also possible, but unsure about this, that I tried installing HL2.
In short ended up with unending prompt and the same issues as listed in original post.
Looking into resetting, using pwr+vol.dwn. Is that what was meant by re-flashing, or that's something harsher? Couldn't find what 'nanding' means.
Also, the N1 is not rooted, whatever that means again.
Ended up eventually resetting phone to factory values. Reconfiguring phone now..
Actually, if you're fast enough you can stop this fc loop.
You need to get to Settings | Applications | Manage Applications and then clear the defaults for HelixLauncher so that you can select the regular launcher.
But how with constant fc? I did it this way:
When HL fc's it will briefly throw you out to the last screen you had active before it tries to reload (you only get half a second or so). The time that you do get should be enough to enter one or so commands... so after fc #1, press close then quickly hit the menu button and 'Settings', HL will launch again and fc again, after pressing close you should see the settings page, hit Applications, HL will launch again and fc, press close and hit Manage Applications... etc, etc.
Painful but perhaps better than a rebuild if you have no other way.
YMMV
Yeah, I tried, but wasn't fast enough. It's like the wild wild west.. the slowest gun lost.
It seems either Android or the launcher should offer a more graceful bailout in scenarios like this. Seems like a serious bug to me. And I've written a few of those myself..
EkoTonic said:
Yeah, I tried, but wasn't fast enough. It's like the wild wild west.. the slowest gun lost.
It seems either Android or the launcher should offer a more graceful bailout in scenarios like this. Seems like a serious bug to me. And I've written a few of those myself..
Click to expand...
Click to collapse
lol, yeah, the gun slinging took me a bit of time!
And the problem is a recognised one BUT the instructions are clear... wipe the data before reverting from Helix to stock and when upgrading roms... the dev has tried to put failsafes in but short of deleting the data there are few options...
But, since the warning is in place, I don't think we can call it a bug, rather an understood limitation... painful nevertheless.
PS - if you've got Set CPU installed you could try and get to that and set your speeds a low as possible, this will give you more time... still requires the gun though.
Did you install it as a system app? Launcher2.apk ?
The suckiest option is to always do a factory reset, as long as you didn't flash the helix launcher. This will delete the Helix Rom, but it will also delete everything from your phone. Proceed with caution!
britoso said:
Did you install it as a system app? Launcher2.apk ?
Click to expand...
Click to collapse
Installed from app store. Went searching for Helix and got 2 versions. Installed 1st and was trying to figure out how much I liked it. Noticed it made things faster, so I was loving that. But then decided to see if settings->scrn size option allowed me to jam more apps on the front page. So, I was playing with that, I believe {set it to 1?}.
As I would be hitting the Home page, it kept asking me how I wanted to complete that action, Default or Helix? So, I made Helix the default action. Then at one point, I was unable to return to the Home page.
Misery followed..
Now, I see from djmcnz's posting that there is supposed to be some sort of warning somewhere, but none on the App store intro of the app.
In either case, imho, it's not ok for an app to risk this kind of loss of functionality, not to mention data.
FYI, I have not left any of the negative comments that show in the app store. I understand the developers behind this app are proud of their work and rightly so. I however will not risk it again. It's not that important to me to be bleeding edge.
EkoTonic said:
Now, I see from djmcnz's posting that there is supposed to be some sort of warning somewhere, but none on the App store intro of the app.
Click to expand...
Click to collapse
Yes, sorry I was referring to notices in this forum.
I am running an eclair rom on my g1 (latest superbad), but that's not really important. What is important is that I like having the launcher in memory because it lets me get back to the home screen faster (for the most part).
In similar fashion, it takes a long time for the phone app to start when I hit the green button, or when I have an incoming call, and so logically I think that keeping the phone app in memory might fix that issue as well. Technically I could be completely wrong. I don't know. I'm not a developer.
Is this possible/feasible? Would it fix the issue?
Note: In all likelihood this post will result in touchy moderators complaining about how it's in the wrong place, or I didn't search or myriad other posts that I often have to sift through before someone answers the question...But I searched and couldnt find any one asking this question, and I thought it was worth asking. I just don't have the time or energy to try and figure out where or when it is appropriate to post. Maybe it's exactly where it belongs, and it is a worthwhile post, but that would be completely accidental.
hugerobot said:
I am running an eclair rom on my g1 (latest superbad), but that's not really important. What is important is that I like having the launcher in memory because it lets me get back to the home screen faster (for the most part).
In similar fashion, it takes a long time for the phone app to start when I hit the green button, or when I have an incoming call, and so logically I think that keeping the phone app in memory might fix that issue as well. Technically I could be completely wrong. I don't know. I'm not a developer.
Is this possible/feasible? Would it fix the issue?
Note: In all likelihood this post will result in touchy moderators complaining about how it's in the wrong place, or I didn't search or myriad other posts that I often have to sift through before someone answers the question...But I searched and couldnt find any one asking this question, and I thought it was worth asking. I just don't have the time or energy to try and figure out where or when it is appropriate to post. Maybe it's exactly where it belongs, and it is a worthwhile post, but that would be completely accidental.
Click to expand...
Click to collapse
Pre-complaining about others' complaints = lame.
To answer your questions, have you: 1. checked Spare Parts to see if the "keep home app in memory" bit is set? (at the bottom of the list) 2. have you used a task manager like Auto Killer to manage your memory more aggressively ? 3. Have you used a task manager to see dialer.apk's status after using the phone for other stuff? 4. Have you posted this question to the devs/other users of this ROM to see if they have similar problems?
BTW, your config including ROM type/build/version, etc is extremely important.
No doubt someone will complain about the placement of your thread but to be honest some of these people have no lives. Anyway, I don't know if this helps but I exclude my dialer from my task manager and it starts instantly. I am using Advanced Task Manager... hope it works for you.
rynosaur said:
Pre-complaining about others' complaints = lame.
Click to expand...
Click to collapse
Calling me lame when it appears that you didn't even read my post=the reason why I hardly ever post here. Ugh.
rynosaur said:
To answer your questions, have you: 1. checked Spare Parts to see if the "keep home app in memory" bit is set? (at the bottom of the list) 2. have you used a task manager like Auto Killer to manage your memory more aggressively ? 3. Have you used a task manager to see dialer.apk's status after using the phone for other stuff? 4. Have you posted this question to the devs/other users of this ROM to see if they have similar problems?
BTW, your config including ROM type/build/version, etc is extremely important.
Click to expand...
Click to collapse
I think maybe you only read the part where I precomplained... since that seems to be the only item you commented on appropriately. But to answer your questions...
1. I clearly stated that I keep home app in memory because I like the performance gain. I have no idea what your asking me.
2. I don't use task killers/memory managers. Cyanogen and most other experts have argued against them enough to convince me that it's not the right solution.
3. huh?
4. I'm not complaining. This is not geared toward any particular dev. Slow phone is a known inconvenience with all eclair builds on G1. Didn't think I needed to go asking if anyone else was experiencing it. I have flashed so many eclair roms to my phone, and with all of them the phone app has behaved more or less the same way.
BTW- I also clearly stated that I have a G1 running the latest superbad.
Here's my question again... Would keeping the phone app in memory improve it's performance in the same way that keeping the home app in memory does? If so is there value in including this option in spare parts?
blackvyper said:
No doubt someone will complain about the placement of your thread but to be honest some of these people have no lives. Anyway, I don't know if this helps but I exclude my dialer from my task manager and it starts instantly. I am using Advanced Task Manager... hope it works for you.
Click to expand...
Click to collapse
Thank you for your suggestion... but I'm leery about using task managers/killers based on some of the discussions I've read from some of the expert devs (cyanogen, etc). I suppose if it works, the result is the same. I am surprised no one has asked this question before. I searched quite a bit and couldn't find a mention- on here, and a straight up Google search.
I don't know why I wasting my time on your reply since you're too arrogant to accept advice but here goes in more simple words you might understand.
1. Download task manager
2. Use task manager to see DIALER's status. Is it foreground? Is it background? What is its OOM, what is it PID?
3. Report results on appropriate ROM thread. Ask other users if their experience is similar.
4. In the meanwhile, try keeping alive the Dialer longer than normal. This means make OOM higher. (yes, its extension is APK as it is an Android application, you know, your OS?)
If you saw "kill" anywhere in there, let me know. If you are comparing your experience with dialer to a Launcher app that is held in memory by Spare Parts, that's useful information. Nevermind that a Launcher that is held in memory elbows out other foreground apps like, oh . . . Dialer? What would you guess that OOM is? If you like launcher's response better than dialer, perhaps you should adjust's dialer's OOM. Just a thought. I don't know ****, that's why I'm trying to help.
rynosaur said:
I don't know why I wasting my time on your reply since you're too arrogant to accept advice but here goes in more simple words you might understand.
1. Download task manager
2. Use task manager to see DIALER's status. Is it foreground? Is it background? What is its OOM, what is it PID?
3. Report results on appropriate ROM thread. Ask other users if their experience is similar.
4. In the meanwhile, try keeping alive the Dialer longer than normal. This means make OOM higher. (yes, its extension is APK as it is an Android application, you know, your OS?)
If you saw "kill" anywhere in there, let me know. If you are comparing your experience with dialer to a Launcher app that is held in memory by Spare Parts, that's useful information. Nevermind that a Launcher that is held in memory elbows out other foreground apps like, oh . . . Dialer? What would you guess that OOM is? If you like launcher's response better than dialer, perhaps you should adjust's dialer's OOM. Just a thought. I don't know ****, that's why I'm trying to help.
Click to expand...
Click to collapse
I don't know where the arrogance was in my opening post??? You decided to start off your first reply with name calling. Cool it. Don't waste your time on me anymore, ok? I don't need your help, man. There's plenty of polite, helpful people here. I'll look to them. I don't need advice wrapped around names and swears and put downs.
Edit:I just deleted 3 paragraphs... you're just not worth the effort.
Let me repeat my question, slightly reworded, since I don't know what OOMs are and I don't want to know.
Spare parts has an option to keep launcher in memory. Is there a chance that adding another option to keep the phone in memory might help with phone app performance? I don't want to use task killers, etc.
That is my question. My only question. Sorry for all of the drama, folks.
hugerobot said:
That is my question. My only question. Sorry for all of the drama, folks.
Click to expand...
Click to collapse
Yes, I'm sorry for my part -- I started sarcastic and then thing flew out of hand. My point about priority and memory allocation is this: dialer is, by its nature, held in memory-it doesn't have to be loaded after boot, it just has to be recalled. I'm sure you've noticed that no matter what you're doing on the phone, it all takes a backseat to an incoming call, and usually very quickly, <5 seconds. The phone is still built to take calls above any thing else.
So my answer to your question is this: bump up the priority of phone.apk. It will respond to the green button more quickly. In my ROM, Phone has an OOM of -12, while HTC Sense is 0 -- that's Spare Parts working to make dialer higher on the food chain. Think about it. Don't wait for someone to rewrite a ROM, just use AutoKiller to bump it up the foodchain and push other background processes further to the back. If you use compcache, remember dialer.apk may end up there, where it takes more till (being compressed) than normal to recall. Also Phone Prioritizer (which I can't find on the market anymore due to my build) is nice fore renicing more frequently than the OS does by default. All these things could help. Reducing other concurrent background tasks will help as well.
hugerobot said:
I don't know where the arrogance was in my opening post??? You decided to start off your first reply with name calling. Cool it. Don't waste your time on me anymore, ok? I don't need your help, man. There's plenty of polite, helpful people here. I'll look to them. I don't need advice wrapped around names and swears and put downs.
Edit:I just deleted 3 paragraphs... you're just not worth the effort.
Let me repeat my question, slightly reworded, since I don't know what OOMs are and I don't want to know.
Spare parts has an option to keep launcher in memory. Is there a chance that adding another option to keep the phone in memory might help with phone app performance? I don't want to use task killers, etc.
That is my question. My only question. Sorry for all of the drama, folks.
Click to expand...
Click to collapse
I know what you mean. Im not sure what happend to XDA lately. Back when it was ALL windows mobile forums (phones no android), everyone was very helpfull ect... When android phones started coming out that brought the whole world to XDA and now we have people on here who have nothing else to do but bash people instead of helping them... Anyways... LOL
As for the dialer / home in memory situation. I found that enabling swap / compcache makes a huge difference.
I been on every 2.1 rom on G1 and ALL of them had problems with loading apps very slow and opening the home screen real real slow even with "Home in Memory" checked in spared parts.
And then I flashed Super E yesterday wich is a 2.1 rom that has swap / compcache settings inside spare parts. I partitoned my sdcard with 254mb swap and enabled Swap and Compcache of 32mb. I also went to the market and downloaded "Swapper 2" which will also enable swap and tell you your swap statistics. After doing that everything and I mean everything opens rather instantly.
My sdcard is class 2 so I never been a fan of using swap but using swap with compcache makes a huge performance difference for me on my G1 on the Super E rom. I think theres an update to Super E that I havnt flashed yet but with the perfomance so far I dont see a need to update but I might update just for the hell of it.
Long story short. Enable swap partition on your SD card / Install Super E / Install Google Apps / Enable Aps 2 SD / Spare Part Enable compcache / swap 32mb / Enable Launcher in memory / Download Swapper 2 from market and set to on.
Thank you. I will try your suggestion.
One last comment- since I started running eclair roms on my G1, the phone app has taken longer to load than it used to. It doesn't feel like it has priority over the other apps. I do need my phone to be a phone, first and foremost, and it has gotten better, but it's still often very slow to load. Also, I run a very vanilla install. I wipe my phone so often that I don't bother loading a lot of apps. This behavior would be typical for anyone with a fresh install of one of the eclair roms.
hugerobot said:
Thank you. I will try your suggestion.
One last comment- since I started running eclair roms on my G1, the phone app has taken longer to load than it used to. It doesn't feel like it has priority over the other apps. I do need my phone to be a phone, first and foremost, and it has gotten better, but it's still often very slow to load. Also, I run a very vanilla install. I wipe my phone so often that I don't bother loading a lot of apps. This behavior would be typical for anyone with a fresh install of one of the eclair roms.
Click to expand...
Click to collapse
All these replies you are getting about phone.apk and dialer.apk have nothing to do with your problem. In fact there is no dialer.apk. And phone.apk is mainly for incoming calls. The rest of the dialing, such as when you use the green button, is done via contacts.apk. The slow load times are really a part of the way android kills processes. If you are running a replacement launcher like LauncherPro or GDE, etc, what you are seeing is that acore needs to reload and takes a long time. The stock launcher is much more forgiving. I have found that by installing the "DialerOne" dialer from the market, that these alternate launchers do not cause the acore reload, and the dialer is very fast to load.
bkmo said:
All these replies you are getting about phone.apk and dialer.apk have nothing to do with your problem. In fact there is no dialer.apk. And phone.apk is mainly for incoming calls. .
Click to expand...
Click to collapse
I never said phone.apk but I did transpose dialer and phone as interchangeable names for the same process. My fault, but what runs in the background to let let you make phone calls is name com.android.phone.
This advice/his characterization of how the dialer-contacts tool works might hold true in Eclair/2.1 Cyanogen-based ROMs, but it is not an "android" universal truth. I am running a Sense 2.1 ROM and believe me, there is no "contacts" process. Foregrounding com.android.phone brings up the dialer, and decreasing its OOM brings up the dialer instantly when the green button is pressed.
The other gentleman's response that more cache is the answer may be a great answer for cm5.0.7 ROMs--if you can get a good cache going, I never could--but it's almost a non-question in Sense ROMs since everyone will run one anyway, whether it be backingswap or linux-swap.
Now that's we've cleared this question up completely
I couldn't bother reading all of the back and forth stuff, I am using Xtreme-1.2.2-black it is 2.1 CM5 base.
I have been using shadowch31 Renice Script that gives the "phone" app a higher priority and it starts up a lot faster.
Also using and ogg file instead of an mp3 has been know to help.
I haven't seen the script in any of the forms so I am not sure if shadowch31 wants it released so pm me or him if you want to give it a try
This is from the getting hero to run faster thread in general:
You can easily lock home into memory. *thanks speedysilwady and firerat. Here's how to set this permanently:
Code:
adb pull /init.rc
[I]replace "setprop ro.HOME_APP_MEM ..." with:[/I]
[I][B]setprop ro.HOME_APP_MEM 1536[/B][/I]
adb push init.rc /sdcard/init.rc
adb shell
# mount -o remount,ro rootfs /
# cat /sdcard/init.rc | tee /init.rc
# mount -o remount,rw rootfs /
# rm /sdcard/init.rc
Can't we do something similar with the phone.apk?
SuperBad v1.4.2 will be up in a bit...
It'll be fixed.
In Christ
Clay
htcclay said:
SuperBad v1.4.2 will be up in a bit...
It'll be fixed.
In Christ
Clay
Click to expand...
Click to collapse
From the man himself! So did my suggestion help? Did I actually contribute by posing the question?
For the record, I did say that this was the case with all 2.1 roms I've tried, not a problem with superbad.
rynosaur said:
This advice/his characterization of how the dialer-contacts tool works might hold true in Eclair/2.1 Cyanogen-based ROMs, but it is not an "android" universal truth. I am running a Sense 2.1 ROM and believe me, there is no "contacts" process. Foregrounding com.android.phone brings up the dialer, and decreasing its OOM brings up the dialer instantly when the green button is pressed.
Click to expand...
Click to collapse
You are right, there is no "contacts" process. And I have seen this contact.apk loading issue since "donut", so it is not an "eclair" only issue. What I do see is that when you are running an alternate home app, that when you press the green button, or the phone icon, what you get is an "acore has died" in adb logcat. At this point acore reloads all the programs under it including launcher, before it runs the contacts app to get you the dialer. I have seen up to 20 seconds before the dialer comes up. Renicing phone.apk does not help this issue in my testing. I have just tried dialerone from the market, and it does not suffer the slow load times. I do not know what brings up the dialer when you press the button, all I know is that the dialer is included in contacts.apk, and what I see in a logcat whn I press the button or icon. Dialerone is working for me, and I can use the latest ADW launcher without a delay to the dialer. Thanks for setting me straight....seriously.
mejorguille said:
This is from the getting hero to run faster thread in general:
You can easily lock home into memory. *thanks speedysilwady and firerat. Here's how to set this permanently:
Code:
adb pull /init.rc
[I]replace "setprop ro.HOME_APP_MEM ..." with:[/I]
[I][B]setprop ro.HOME_APP_MEM 1536[/B][/I]
adb push init.rc /sdcard/init.rc
adb shell
# mount -o remount,ro rootfs /
# cat /sdcard/init.rc | tee /init.rc
# mount -o remount,rw rootfs /
# rm /sdcard/init.rc
Can't we do something similar with the phone.apk?
Click to expand...
Click to collapse
AFIK phone.apk is not the dialer, and is already locked and does not get killed. Just think about it, if it was able to be killed, what would be running to handle an incoming call?
bkmo said:
Thanks for setting me straight....seriously.
Click to expand...
Click to collapse
Hey, everybody's got to be wrong at least once a day, me . . . . more 10 or 20 times a day. I don't know what it is with gapps and acore crashing regularly in cm eclair builds, but my impressions from t1-stable were: Hero-like instability, without the Hero bells and whistles. So I switched to Sense 2.1 Result, apps do die when I look at the phone funny (or press Dial -- fring dies when I press dial, or the mysterious com.smithmicro.DM -- probably a keylogger), but the bells and whistles are nice, so there's tangible payoff for dealing with a stretch of a mod.
Hope HTCClay works a miracle and fixes your phone. Maybe he can share the secret with other devs Peace
rynosaur said:
I don't know why I wasting my time on your reply since you're too arrogant to accept advice but here goes in more simple words you might understand.
1. Download task manager
2. Use task manager to see DIALER's status. Is it foreground? Is it background? What is its OOM, what is it PID?
3. Report results on appropriate ROM thread. Ask other users if their experience is similar.
4. In the meanwhile, try keeping alive the Dialer longer than normal. This means make OOM higher. (yes, its extension is APK as it is an Android application, you know, your OS?)
If you saw "kill" anywhere in there, let me know. If you are comparing your experience with dialer to a Launcher app that is held in memory by Spare Parts, that's useful information. Nevermind that a Launcher that is held in memory elbows out other foreground apps like, oh . . . Dialer? What would you guess that OOM is? If you like launcher's response better than dialer, perhaps you should adjust's dialer's OOM. Just a thought. I don't know ****, that's why I'm trying to help.
Click to expand...
Click to collapse
there must be some mod out there to shut up this silly stupids like this guy...why this people ever answer in a post?!!!!
So a fair amount of people are using Androidiani Open Recovery, myself included now, but I have a few questions about it. Namely what everything does. In the menu there are all sorts of things to do and use, but I am not sure what they actually do. I know about memhack, kernal optimization and zipalign, but what about all the other Froyo mods and tweaks in there?
For some reason, I can't attach a screen shot to this, but some of them are Istall Mod -conservative/interactive, Memory manager, vm heap size,...
The most helpful feature of AOR is the possibility to check the sd card. No need to plug the card to the pc for checks.
I also use zipalign after restoring my apps in a new rom.
With the adblock script you can update the host file to prevents ads in apps or in browser.
So, the one thing about Androidiani is that it's developed by A853 users, so I've never touched the baseband utilities out of fear it will do something bad.
It's nice to have access to system apps to get rid of what I don't want (or pull out a system apk) after a new flash. I also keep a copy of the latest system apps as a theme so after a new flash I can just apply the "theme" & have all the current versions of Maps, Facebook, etc.
I've never tried the kernel optimization because I wasn't' sure if I should use the froyo or the eclair as we still have the eclair kernel.
Mioze7Ae said:
So, the one thing about Androidiani is that it's developed by A853 users, so I've never touched the baseband utilities out of fear it will do something bad.
Click to expand...
Click to collapse
I know better than that. Baseband messing is Badddd! I am more interested in the Memory tweaks and things like that.
I've never tried the kernel optimization because I wasn't' sure if I should use the froyo or the eclair as we still have the eclair kernel.[/QUOTE]
I tried the one for Froyo and not sure if it worked or not but let's just say it didn't "screw" anything up (as far as I know). I did have to re-root though and re-allow all the superuser permissions and overclock again. But as far as performance, it didn't hinder anything and it might be a plecebo effect, but I feel it is somewhat more stable. Could be in my head though.
Mioze7Ae ~ This is one of those times I was talking about in the SUperoneclick question where I had to use Unversal Androot and it worked just fine.
Mioze7Ae said:
So, the one thing about Androidiani is that it's developed by A853 users, so I've never touched the baseband utilities out of fear it will do something bad.
Click to expand...
Click to collapse
They don't work, neither does that fix permissions stop force close just bricks the phone...
ZipAlign works fine though...
hellmonger said:
They don't work, neither does that fix permissions stop force close just bricks the phone...
Click to expand...
Click to collapse
Fix permission will work if it was a permission problem.
Got a question about this. After a few weeks of flashing the special, Wanhu, CM6...I noticed that AOR wouldn't let me flash update.zips for some reason. Awhile ago, I had this problem and either 3rdstring or Mz advised me to reinstall AOR. I did and everything worked. Now that the the CM6 is out and primarily done through updated.zips, I found a problem again. When AOR installs, it loads up a bunch of pix that show up in my media gallery. If I leave them in there, I can use the update.zip just fine. If I delete these pix, then it creates the problem that will not let me use that function. I can probably put a .nomedia in there somewhere, but not sure where. Has anyone else had this problem. It is AOR 3.3 in case you are wondering.
I read through this thread a week back. Im now using Androidiani with stock CB 2.1 Could anyone please guide me to which optimizations to use with 2.1, how they work and what works on our XT720? I would really appretiate it thanks!
sohrab.naushad said:
I read through this thread a week back. Im now using Androidiani with stock CB 2.1 Could anyone please guide me to which optimizations to use with 2.1, how they work and what works on our XT720? I would really appretiate it thanks!
Click to expand...
Click to collapse
What I have used is the Zipalign, obviously the wipes and resets, the fix permissions works really well (especially when flashing in between ROMs), Mchlbenner uses the Overclock settings. Haven't used anything in the memory settings like VM heap or anything like that.
Probably the things I use the most are in the menu utilities and the SD and SD-ext scans to make sure card is working. I usually do this before I flash a ROM and then once after I boot up totally. Seems redundant but it has saved me a card before b/c of a bad partition.
Mioze added a script for link2sd/app2ext (http://forum.xda-developers.com/showthread.php?t=1177020&page=61) sorry don't know how to put just a plain "here" and have the link embedded.
If you use any of the modding menus, use the Eclair one b/c it is based off the kernal version. I know that 3rdstring uses AOR quite often to apply apps and such. May want to ask him about setting that up.
Woodrube said:
Mioze added a script for link2sd/app2ext (http://forum.xda-developers.com/showthread.php?t=1177020&page=61) sorry don't know how to put just a plain "here" and have the link embedded.
Click to expand...
Click to collapse
That's more of a WIP for discussion. The ROM has to support it (and none do yet).
Mioze7Ae said:
That's more of a WIP for discussion. The ROM has to support it (and none do yet).
Click to expand...
Click to collapse
My bad. Sorry about that one MZ.
Sohrab ~ forgot to mention to stay away fro mthe baseband settings. Pretty sur ethis will mess your stuff up if you don't know what you are doing with it. Better left alone (for now).
Woodrube said:
My bad. Sorry about that one MZ.
Sohrab ~ forgot to mention to stay away fro mthe baseband settings. Pretty sur ethis will mess your stuff up if you don't know what you are doing with it. Better left alone (for now).
Click to expand...
Click to collapse
Thanks woodrube! I tried a few things, have no idea if they are working or not. Adblock doesnt work, still get ads with wifi when i play angry birds. Also google maps is uninstallable on the market. Wonder what thats about.
Woodrube said:
My bad. Sorry about that one MZ.
Sohrab ~ forgot to mention to stay away fro mthe baseband settings. Pretty sur ethis will mess your stuff up if you don't know what you are doing with it. Better left alone (for now).
Click to expand...
Click to collapse
No problem. I think it's time we start creating our own baseband files for XT720. I've been poking around inside the Androidiani ones. I think they're just updates that only mess with the /system partition, so maybe worst case your phone stops working with the network until you get the right baseband back in. I think I know where to extract files from the SBFs to create our own, so we should be able to start making some XT720 specific ones.
sohrab.naushad said:
Thanks woodrube! I tried a few things, have no idea if they are working or not. Adblock doesnt work, still get ads with wifi when i play angry birds. Also google maps is uninstallable on the market. Wonder what thats about.
Click to expand...
Click to collapse
I think the hosts file in the adblock is way old by now. At least it seems I start to get ads every few weeks and have to install a new hosts file. I just hosed my phone so I can't check, but I think AdFree is the app I use for that.
I already made baseband update for our phone. I used one from androidian and replace our files with theirs.
Sent from my Milestone using XDA App
I figured out the maps issue. Apparently the new version of google maps has 3D maps and wasn't avaibable in my country. I just used market enabler and downloaded it. Lol its stupid, I mean dont let someone update just because of country they live in? Ill wont have 3D at home, but I can use it if i travel abroad. Anyways!
I use adfree too but the recent update screwed everything up. I just revert to previous build using TB and it still works for me. If I can pull that one out ill pm you with it, since not thread relavent. Btw ads in Angry Birds are embedded in software, so adfree wont work for some reason. Check adfree's review in market and they tell you why.
Has anyone used the compress option when making a back up? It is there, but I wonder what it will do? Does it function properly? I seem to remember reading something about compressing ad back up and it get corrupted or something like that but I can't remember when or where I read it.
What functionality does the Compress back up do (and please do say something like "it makes it smaller")? Does it work?
Now that we've got some Sunshine in our lives, sadly (not really) it is time for Turboid to be retired. We don't need it anymore.
If you would like to set up a rom on your unlocked Turbo that has all the features that Turboid had, upgrade to SU4TL-44, unlock with Sunshine, install TWRP, and flash following:
1. SuperSU: https://download.chainfire.eu/696/SuperSU/
2. Busybox: http://forum.xda-developers.com/and...-busybox-v1-23-2-stericson-flashable-t3114476 (NOTE: This is not the latest version, but you need to have busybox flashed before you flash Pon-3. Once you boot the phone, use Busybox Installer by Stericson in the Play Store to update to the latest version).
3. Pon-3: http://forum.xda-developers.com/showthread.php?t=2530976
4. Xposed Framework: http://forum.xda-developers.com/showthread.php?t=3034811 (Make sure to flash the correct SDK for the rom that you're running. SDK21 = Lollipop 5.0.X. SDK22 = Lollipop 5.1.X. SDK23 = Marshmallow 6.X. Also, always use the ARM version.)
5. iOS 9.1 emojis: http://forum.xda-developers.com/nexus-6/themes-apps/mod-ios-emojis-android-t3231571
Once all that's flashed, let the phone boot up. Wiping cache and dalvik cache is always a safe bet after flashing anything. Once it boots, do the following:
1. Go back to the Xposed page and install the Installer apk.
2. Get Adaway here: https://f-droid.org/repository/browse/?fdid=org.adaway (Install using the default settings. No need for redirecting the hosts file anymore.)
3. Better Battery Stats is here if you like: http://forum.xda-developers.com/showthread.php?t=1179809
4. The Turbo 2 command center is here: http://forum.xda-developers.com/droid-turbo/themes-apps/droid-turbo-2-command-center-root-t3244386
I think that about covers it. Go forth and flash! Thanks for letting me play dev for a few months.
Thanks to:
@computerfreek274 for his excellent roms, his dedication to them and for our SELinux discussion
@JulesJam for her various guides and posts that taught me how to do most of this
@btdownloads7 for answering my question about the HDR bug
@DespairFactor for the iOS 9.1 emoji port
@mrchezco1995 for showing myself and the world how awesome ponies can sound via Pon-3
And at long last, thanks to @jcase and @beaups for kicking Motorola and Verizon in their bootloader-locked balls!
Awesome man. Nice to have some options, even if they are fairly similar. Thanks. :good:
my2cents said:
Awesome man. Nice to have some options, even if they are fairly similar. Thanks. :good:
Click to expand...
Click to collapse
No prob! If you can think of anything else that you would like me to add to it, let me know.
TheSt33v said:
Unlike the other images floating around, I started off with the stock SU3TL-39 system image from the full Verizon firmware. To the best of my knowledge, the other roms are based off of firstEncounter's 5.1 image, which was obtained in a different way. Does this matter? Probably not, but at the time I thought that this might fix the HDR bug, and it did, but probably not for that reason.
Click to expand...
Click to collapse
There's a SU3TL-39 full firmware? My images were based on the SU3TL-38 and updated to SU3TL-39 by emulating the OTA script.
(Also, HDR works on my images, for whatever it's worth)
Regardless, always glad to see more development for the Turbo!
firstEncounter said:
There's a SU3TL-39 full firmware? My images were based on the SU3TL-38 and updated to SU3TL-39 by emulating the OTA script.
(Also, HDR works on my images, for whatever it's worth)
Regardless, always glad to see more development for the Turbo!
Click to expand...
Click to collapse
Yep! You can get it on the motofirmwares website. Yeah, someone confirmed for me the other day that it works on your image now. In the past, I had flashed it and it didn't, but you've updated it since I did that. So I guess HDR working isn't really a feature anymore. I'm working on some gimmicks to make my image a little more relevant though.
Would it be possible for you to allow us to claim space to the area where the Google Search Bar is, when it is hidden? Also, I would like to be able to clear all the open applications without having to swipe them all one at a time. Is that possible?
my2cents said:
Would it be possible for you to allow us to claim space to the area where the Google Search Bar is, when it is hidden? Also, I would like to be able to clear all the open applications without having to swipe them all one at a time. Is that possible?
Click to expand...
Click to collapse
I'll look into the Google search bar thing. I've never seen my screen without it, so I didn't know that the space wasn't automatically used. As for the clear all recents thing, that is one of the many features of Gravity Box for LP (a well known xposed module). Try that. I'll see if there's a way to bake it into the rom too.
I posted on the other thread about this, but I will say again here, this img is great. Has similar battery life to the other Lp img I was running, despite not having tweaks. I unplugged at 530 am. been kicking butt all day long. I streamed via Bluetooth for 2 hours driving at work, and noticed better 4g signals than I have had yet at my work using this img. There were zero glitches or bugs that I noticed. I am still at 8% battery, atm. I had a crapload of SOT. Look for yourself. amazing img. thank you!!!
p.s. I just noticed I have had max brightness all day as well. lol.
I just realized you removed the corporate email app (after a day or use, haha). Is there a way that I can side load it or something? I love the debloated ROM, but that is one app I need for my college email account.
Also, is it ok to update Moto Actions? You can understand why I ask that!
^^^ I used the Outlook app as a replacement today. Gmail also will allow you to add other email accounts now, so that may be why. As far as requests, my only one may not be reasonable or practical, but it would be a deodexed version of this. Again, awesome work.
Yeah, specifically, I need the exchange piece. I tried the outlook app, but it doesn't handle certain things as well. I also tried installing Google Email 6.5 as well as the Exchange Services apk, but I know I have to be missing something... Actually, probably lots of things! haha.
Also, adaway doesn't work with this build, is that right?
kitcostantino said:
I posted on the other thread about this, but I will say again here, this img is great. Has similar battery life to the other Lp img I was running, despite not having tweaks. I unplugged at 530 am. been kicking butt all day long. I streamed via Bluetooth for 2 hours driving at work, and noticed better 4g signals than I have had yet at my work using this img. There were zero glitches or bugs that I noticed. I am still at 8% battery, atm. I had a crapload of SOT. Look for yourself. amazing img. thank you!!!
Click to expand...
Click to collapse
Awesome! I'm glad it works well for someone other than me.
kitcostantino said:
^^^ I used the Outlook app as a replacement today. Gmail also will allow you to add other email accounts now, so that may be why. As far as requests, my only one may not be reasonable or practical, but it would be a deodexed version of this. Again, awesome work.
Click to expand...
Click to collapse
Well if you need the stock email app, I can send an image your way that has it once I find some time. I have no idea what deodexing roms entails, but that sounds like a fun project too. I'll look into it.
my2cents said:
Yeah, specifically, I need the exchange piece. I tried the outlook app, but it doesn't handle certain things as well. I also tried installing Google Email 6.5 as well as the Exchange Services apk, but I know I have to be missing something... Actually, probably lots of things! haha.
Also, adaway doesn't work with this build, is that right?
Click to expand...
Click to collapse
Correct. I didn't put adaway in there. I probably could though. Stay tuned.
my2cents said:
I just realized you removed the corporate email app (after a day or use, haha). Is there a way that I can side load it or something? I love the debloated ROM, but that is one app I need for my college email account.
Also, is it ok to update Moto Actions? You can understand why I ask that!
Click to expand...
Click to collapse
Haha yes, updating seems to not cause the apocalypse to occur this time around. I'll make an image that has the stock email app intact, or I'll try sideloading it and post the apk if it works.
my2cents said:
I just realized you removed the corporate email app (after a day or use, haha). Is there a way that I can side load it or something? I love the debloated ROM, but that is one app I need for my college email account.
Also, is it ok to update Moto Actions? You can understand why I ask that!
Click to expand...
Click to collapse
I added the stock email app back. Side loading didn't work. Will be up in a few hours.
thats cool. honestly, deodexing is removing all of the .odex files from the rom. (located at /system/app , system/priv-app, etc.
the reason i ask about it is it would make theming easier. mind you, without system r/w access, it is a moot point. it may make the theme options available work better though. (LPthemer module comes to mind). CF has said he will not be doing that at any point, so it may be a PITA.
kitcostantino said:
thats cool. honestly, deodexing is removing all of the .odex files from the rom. (located at /system/app , system/priv-app, etc.
the reason i ask about it is it would make theming easier. mind you, without system r/w access, it is a moot point. it may make the theme options available work better though. (LPthemer module comes to mind). CF has said he will not be doing that at any point, so it may be a PITA.
Click to expand...
Click to collapse
Oh. That's it? I can do that in 2 seconds. I thought there was something more to it.
1.02 looks like the perfect ROM for me! Thanks @TheSt33v