yashsingh1/xdaforums huggingface dataset:
[Touch CDMA General] tatnai:
i agree, the power off function is intermittent. If it is going to work, it takes a while to work. But for me probably 60-75% of the time it does not power off no matter how long I wait.

Waking up from sleep occasionally takes a few presses of the power button - this is due to the new bundle files, not the system.sqsh i believe. When vilrod initially made the new button config, we had this problem, then he fixed it. will post in mssmison's thread about this, but just so everyone knows this is not a problem with the system.
[Touch CDMA General] tatnai:
I upgraded to latest xROM at the same time as changing to the 9-6-09 bundle. Everything now seems a touch slower to me . . . returning to home, completing actions within programs. Will try increasing my compcache in the user.init file and see if this helps.
[Touch CDMA General] zenulator:
I think its the rootfs and not my system image. Try turning off compcache.
[Touch CDMA General] tatnai:
i'm also getting a bunch of force closes/waits, so i'm just going to rebuild my data.img with all the new stuff, sounds like that worked for someone above.
[Touch CDMA General] zenulator:
You probably should everytime you start using a different system image.
[Touch CDMA General] tatnai:
new data.img made no diff (i was switching from you prev xROM anyways, didn't expect much). I kept the latest .sqfs xROM, switched to sqashfsbasefiles.zip that had been posted a while ago instead of the newest bundle, and I am getting much better results - more responsive, no more wakeup problem. I don't know what it is with the latest combined work-with-everything bundle, but it is not working for me - I just can't keep using it. There don't seem to be any other differences - was never using SD swap, compcache was set to the same, it just seems to be the files.

EDIT: so it did solve the slow response problem, but the wakeup problem remains. Is this a problem with files from mssmison?
[Touch CDMA General] zenulator:
There's a lot of changes going on and I don't really care for most of them. But it's out of my hands. Truthfully I don't see much of a difference in squashfs/cramfs and I don't really care if my builds work with kaiser wifi. I just want things to be stable and work for my phone. I'm using the rootfs.img and initrd.gz and zImage thats in my vogue-hero bundle and it's working fine. I've also stopped using compcache/swap in hero.

I've got a donut build from source that I'm working on for personal use. It's going to have it's own initrd.gz and rootfs.img. I might just make a initrd.gz and rootfs.img just for xrom since thats the only other build I have out besides hero. I'm sure everything will sort it's self out. But if want to turn compcache off. I don't think xrom needs it.
[Touch CDMA General] tatnai:
would love to test for you when it is done. i hope you plan on releasing it, will look forward to it.
[Touch CDMA General] refthemc:
X2......Also for the whole squash/cramfs thing. Ive found a perfect swap setup that works for me and i really dont feel like changing it. Once again thanks for the whole userinit thing zen
[Touch CDMA General] fixxxer2008:
whens that new build come out zen we were talking about? i love android but every time i use it, i can't go more than a day without not receiving calls and the data connection dropping. as of right now ill probably just stick to winmo but i also know when you release another build ill keep trying. what bundle do you recommend i use?
[Touch CDMA General] fixxxer2008:
whats that userinit do anyways? is it needed?
[Touch CDMA General] jamezelle:
i work at a office and i have been calling my phone from the office phone, and it rings to voicemail before it even shows up on my phone phone(android hero latest release). it doesnt even ring on my phone in time. its a shame because hero is so darn sexy lol oh well i guess
[Touch CDMA General] fixxxer2008:
glad to see im not the only one having issues with this. i use my phone for work so i can't miss calls, thats why i have to use winmo for now. i hope the real htc hero phone runs and works alot better?
[Touch CDMA General] jamezelle:
i just ran the renicer script in gscript and there was no change.:(

no incoming phone calls for me with hero:(

EDIT:sorry i know this is the wrong thread i was just going with the discussion.
[Touch CDMA General] zenulator:
The latest hero?
[Touch CDMA General] jamezelle:
yes the latest hero sqfs bundle. the call shows up on the device right as it is going to vm
[Touch CDMA General] tatnai:
actually today once again I rang my phone five times in a row and went straight to voice mail each time. had service, was roaming with great service at the time. as soon as I woke it up, it received calls just fine. using latest xrom with pre re nicer sqsh bundle. I was wondering if the re-nicer would make a difference but from the above post it does not seem so. I think that this problem and the missed SMS message problem are likely the same, I was going to give the re-nicer a try before calling it quits with android. as much as I love it, I've got to get my SMSs and calls.
[Touch CDMA General] pmos69:
You have to understand this is a problem that affects a lot of android ports (specially Hero) to all devices (vogue/kaiser, Sapphire, Dream).

There are a number of things that have been referenced to minimize this problem (with mixed results):

- renice those processes

- turn off vibration for received calls

- use ogg ringtones

- the usage of some specific applications

If you find anything that helps, feel free to contribute.
[Touch CDMA General] tatnai:
What I am speaking to is the problem where there is no sign that a call or SMS has come in at all - it is as if it was never sent, not that there is no notification. Does turning off vibration, using ogg ringtones have an effect on this? it seems doubtfull, but I am happy to give all of these a shot if you think it would help with actually never receiving some SMS messages and calls.
[Touch CDMA General] pmos69:
It's the same problem. What has been observed is that the processes involved take a lot of time to "wake up". some of those things affect that.

renicing the processes

might

improve response time, in some cases.

turning off vibration eliminates a call to one of the processes involved, and since they are all sequential, makes the visual call announcement start faster.

using ogg ringtones usually means reading smaller files from the sdcard.

...

note: these are not things I've experimented myself, but the results of the acumullated experiences of a lot of users. And still, no definitive solution has been found.

You can search the forums for information about this. There are a few threads (for several devices) discussing it.
[Touch CDMA General] fixxxer2008:
this is why im done trying with any android build right now until i decide if im buying a real hero based phone. i also can't afford to miss important work related calls and texts. all these builds to me for now are just to play with occasionally and get used of android until i get a real android phone. it honestly puts a bad taste in some peoples mouth with all of these issues we are having. i hope real android phones don't have any issues. :confused:
[Touch CDMA General] tatnai:
if you read other phone forums, particularly the android forum, you will note that some people do have this problem, not just with android but with other phones as well such as the pre. do a google search on missed sms, or missed sms android. across the board it appears variable between individuals - some people have it, other's do not.

the clincher for me is that with windows, i don't miss anything, and with android no matter what I try (turned off vibrate, turned off sms pop, ran re-nicer, changed sleep mode so the phone does not sleep quite as deep but wastes battery, various system.img, multiple new data.img files, kill programs like a maniac with taskiller, the list goes on) I can't go more than one or two days without missing something. I wonder if it is a problem with the radio turning off or something when the phone sleeps, or with roaming, but everything is so inconsistent (happens while roaming, while not roaming, great signal, poor signal, rarely when phone awake and network disconnected showing "android").

anyways, i'm taking a break from android for this reason, will keep following developments, will try donut to see if the problem is any different, and will be back if windows starts giving me the same problem with extended use (maybe I just didn't notice it before, or it just by chance did not happen while testing back and forth between android and windows). great work has been done here, thanks zen.
[Touch CDMA General] zenulator:
a lot also has to do with the ril that we are using. it's pretty much coded from scratch although it works pretty good with all the different carriers that it supports there is still a lot of work to do to it. i made a hero build that used the htc ril and calls came through pretty quick and caller id worked but because it's closed sourced i couldn't get data working with it although i didn't really try every possibility and i'm by no means an expert when it comes to that. when i put it out i was hoping that somebody would do some experiments on their own to try and get data working with it but i guess nobody had any luck or enough interest in it. right now android on the vogue is still a work in progress. we're just now getting partial bluetooth and the flashable rom project is pretty much at a standstill but looking back at the 1.1 releases i think we've come along way.
[Touch CDMA General] fixxxer2008:
don't get me wrong, i meant no offense as i love android. i just cannot use it for everyday uses as for work and such. i wanted to get used to android in case the hero will be my next upgrade in a few months. right now it's between that, the pre or maybe even the new touch vogue phone? i do despise winmo but i have no choice but to use it for now. i wonder if these issues we are having is because most android based phones are gsm with sim cards and some of ours are cdma? just a thought?
[Touch CDMA General] zenulator:
could be just wait until android has full cdma support. right now there are a lot of work arounds going on to get it to function like a normal phone so some of that might clear up soon when all the android cdma handsets come out. it's still a guessing game for now.
[Touch CDMA General] pmos69:
Been using JACMANxROM1.4r3 for the last day.

- Calls ring almost immediately, even when phone is sleeping. At the start or during second ring tone.

- No missed calls.

- No missed SMS messages.

- No delivery errors.

- No reloads

- Data works flawlessly

- (Wifi works on my Kaiser)

... all that and it's super fast.

Using system-xrom1.4r3.sqsh + basefiles-20090908.zip

1st boot without data.img.

basefiles with default settings.

Note: Previous basefiles on the vogue-android were mixed-up because of some weird problem.
[Touch CDMA General] tatnai:
yes, I tried again with bundle posted together with hero files on vogue-hero, including re-nicer, called my phone first thing in the morning, nothing - straight to voicemail. Sent an SMS to it, nothing. Turned the phone on, no evidence that either event had occurred. I'm wondering if this is a CDMA problem with the current ril, since many people don't seem to have it at all . . . who knows. whatever the problem is, it just won't work reliably enough for me right now.
[Touch CDMA General] jamezelle:
dont feel bad me either calls dont even show up for me with hero at all.:(
[Touch CDMA General] pmos69:
Since this is not a hero thread, I was talking about:

system-xrom1.4r3.sqsh + basefiles-20090908.zip
[Touch CDMA General] plemen:
Yes please - not to be a jerk about it but can we keep the hero issues / support in the hero thread?
[Touch CDMA General] pmos69:
?

system-xrom1.4r3.sqsh is not a hero build.
[Touch CDMA General] pmos69:
Now that I finally rebooted, just have the problem of it staying infinitively in the "rebooting phone..." screen.
[Touch CDMA General] tatnai:
I know, I used system-xrom, but with squash basefiles included in zen's hero release as this had been suggested by zenulator before and there were postings about issues with the current basefiles. It worked faster and smoother for me than using the 9/6/09 basefiles on vogue-android.
[Touch CDMA General] pmos69:
9/6/09 basefiles were incorrect (some weird problem with the upload)

:-/
[Touch CDMA General] plemen:
heheh - didn't mean you - the posts prior to yours seemed to be about issues running hero. Anyway, I'm not the thread police but just want to see issues posted in the right thread for my benefit as well as others.

cheers.
[Touch CDMA General] fixxxer2008:
i really do think this is an issue because i have a cdma phone. to my understanding the first cdma android phone will be the sprint htc hero?
[Touch CDMA General] zenulator:
i though the vogue was the first cdma android phone ;) quick somebody build a flashable image.
[Touch CDMA General] fixxxer2008:
yeah true!
[Touch CDMA General] KERKEDAGAIN:
I finally ventured away from Hero (for variety not functionality. Hero is still my favorite all around) and am trying all the other builds both yours and mssmison's.

In my travels I found that mssmison's latest sqsh has a SICK custom lock screen..anyway you can include that in your soon upcoming xROM update or is that a no-go?
[Touch CDMA General] bensmiller:
looking good

well I have been between alot of the different builds and im cerrently running your r3 build with the new base files off of the android code page and well its running super smooth and I like the look of it.

The only thing that I think i have run into problems with is that well it seems there is no zoom function on the web browser other than that it seems great. Is that something that is only my problem or is it something I am over looking.
[Touch CDMA General] pmos69:
tap on empty space and it zooms out.

tap on text and it zooms in.
[Touch CDMA General] KERKEDAGAIN:
hmm..it worked for me acessing it from the menu..
[Touch CDMA General] bensmiller:
ughhh I think i am going to have to start with a fresh data image I just been using the one I had set up before and well do you think that would effect the web browser?

And if yes then is there a way to back up all my apps so I dont have to redownload them all.

the tap zoom doesnt work and there isnt a menu featuer for it.
[Touch CDMA General] zenulator:
it's in there....i'm uploading soon.
[Touch CDMA General] KERKEDAGAIN:
y'knoowww...i KNEW it would be in there; meant to edit that post to say "IF you haven't already added it". Greatness..can't wait!!
[Touch CDMA General] tatnai:
i don't like the new lock screen, too busy. whatever pleases the masses, i guess.
[Touch CDMA General] loserskater:
I second that. I like the simple lock screen much better. Will be happy either way, but just thought I'd throw it in there.
[Touch CDMA General] zenulator:
The new lock screen is a part of xRom 1.5r3 that jac releases for the dream. Ill put the finishing touches and release the vogue port later this afternoon.
[Touch CDMA General] skydirt:
Looking forward to the your new xROM build. :D
[Touch CDMA General] refthemc:
v1.5r4 released yesterday.....Love this port Zen, thanks again!
[Touch CDMA General] skola28:
Where? Its not on vogue-android....
[Touch CDMA General] jamezelle:
he means for the dream it was released, here lol
[Touch CDMA General] skydirt:
F5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5 f5.
[Touch CDMA General] zenulator:
ok upload in 5 4 3 2 1.......
[Touch CDMA General] wdbanks:
Great...is the file named JACMANxROM1.4r3 or JACMANxROM1.4r4? When I click the direct download its still has the first name.
[Touch CDMA General] nerraDD:
Looks like it's over at the "vogue-hero" code site, 1.5r4b

http://code.google.com/p/vogue-hero/downloads/list
[Touch CDMA General] tatnai:
I'm assuming we should not use our old xrom data.img with the latest version given the new donut components?
[Touch CDMA General] jamezelle:
im wondering the EXACT same thing
[Touch CDMA General] masalma:
sorry don't mean to be an idiot :) did some reading through the thread and searched a little bit. but which user.conf should I use. Running on vogue right now.

Thanx,

Nas
[Touch CDMA General] tatnai:
it will pick the right one automatically, do not need to change the names of any of the .conf, just put them all on your sd card.
[Touch CDMA General] zenulator:
all I can say is backup your old data.img and try using it.
[Touch CDMA General] tatnai:
yeah, that's my routine before trying anything new with an old data.img. thanks for the update.
[Touch CDMA General] fixxxer2008:
yikes....sorry zen but this build is totally unusable for me on my vogue. slow as a snail, force closes all over the place, phone freezes, apps take 30 seconds to load...etc. also that audio hack did not do much for the in call volume. and yes before you ask i used all of the files from your bundle and a clean data image.

:(

im starting to think i may not end up buying an android based phone after all. im having zero luck with any android build do far.
[Touch CDMA General] zenulator:
I haven't had any of that. Which apps force close? When does the phone freeze? I also uploaded it to vogue-hero and left the other one up at vogue-android because it's using a different base and also using different lowmemory parameters so it's sort of beta right now. The only thing I suggest is to use taskiller and kill some tasks if your starting with a fresh data.img. I might remove the hero themed advanced launcher and just go with the original xrom launcher because thats the only thing giving me trouble.
[Touch CDMA General] fixxxer2008:
figures, it's just me having issues as usual. :mad:

all of the apps, take forever to load up, i get force closes on almost everything too. i did use task killer and it also freezes up. over all it is just super slow for some reason? the last build was not like this at all.
[Touch CDMA General] skydirt:
You're not alone. I am experiencing the same thing on my vogue. I used all the files in the bundle, new keymap zimage and the supplied data file. My force closes are , Messages, CoPilot, clock, weather, market or what ever else I try to start from the home screen. Unfortunately for me, it's not "unusable" because I think it's too slow, but because when it locks up, my screen times out I can not get the screen to come back on, and I have to restart the phone. I also get this error a lot "Activity Select activity (in application Settings) is not responding) I get that error when I try to open anything from the home screen.
[Touch CDMA General] zenulator:
I'll take the build down and work on it. I'll replace the lowmemory parameters with the old ones and put in the original xrom launcher. I had to fix a couple other things anyway. I'm also going to remove the games and added apps and just put them in an extra zip so people can pick and choose which ones they want. I'll have the new build up later on today.
[Touch CDMA General] skydirt:
<3

Thanks Zenulator, looking forward to the new build ^^
[Touch CDMA General] JacenSolo2001:
Same issues with the new build - seems more responsive, BUT force closes on "reporting app", gmail, and several others.....

I like the responsiveness though..
[Touch CDMA General] zenulator:
I'm about to upload a new version.
[Touch CDMA General] jamezelle:
Can't wait for the new release
[Touch CDMA General] wdbanks:
Hate to be a buzzkill...but this build is the absolute best I have run to date out of all the ones I have tried. I love all the new apps and I dont experience any problems what so ever. It runs faster than winmo and I have the latest NFSFAN Vogue rom running...so that means its really fast. I dont have one complaint.
[Touch CDMA General] fixxxer2008:
well your int he minority then.

zen let us know when it's ready to go, ill try one more time.
[Touch CDMA General] zenulator:
uploading now. you need to use the rootfs.img included in the xROM1.5r4c.zip. you also need to either set your apn through the setting/wireless controls/mobile networks/access point names or reboot and the apn will be automatically set so you can use data.
[Touch CDMA General] tatnai:
first version 1.5r4b was slow for me with right files and new data file. force closes too. EDIT: force closes were from market, gmail, calendar. also experienced the no wake-up issue - multiple presses of power button often won't wake up the phone. I was pressing repeatedly for like 10 seconds sometimes. DLing the new 1.5r4c now.
[Touch CDMA General] zenulator:
lol i get it. the new version is up. should be a lot better.
[Touch CDMA General] jamezelle:
and that it is thanks alot zen, another job well done:)
[Touch CDMA General] incubus26jc:
it is very nice man!! thanks
[Touch CDMA General] tatnai:
1.5r4c is much better. with new data.img, speed is fine. still get an occasional wait/force close; process.acore has happened a couple of times, but not that big a deal because it is infrequent and it is running fast.

only issue for me is the wake-up issue that remains. intermittently won't wake up from sleep without multiple presses of the power button.

great work, thanks zen.
[Touch CDMA General] zenulator:
I have the wake up issue to but not only on this build. Are you using the kernel with the new button map?
[Touch CDMA General] jamezelle:
in noticed that this build slows down almost to a halt when installing applications. and sometimes i get market fc/wait.

ive gotten one acore fc but other than that this build is pretty good
[Touch CDMA General] fixxxer2008:
great job zen, it works fast as lightning now, i LOVE the pre style launcher too. best of all my phone works and i can get calls finally. ill test it out tonight and tomorrow and report back. :D
[Touch CDMA General] fixxxer2008:
use the new kernel button mapping zimage, this build works great for me. of course im using my old data image too from his previous build, so maybe that's why mine works soo fast.
[Touch CDMA General] skydirt:
I have the wake up issue as well. Unfortunately even with multiple presses it wont wake up. Other then that all the force closes errors are gone. I am using the zimage with the new mapping. Should I try to use the old mapping also included in the bundle?

I don't even know what the difference between "old" and "new" are.
[Touch CDMA General] zenulator:
The old style keymap just has a different button layout. It's a lot more functional but wears on the volume rocker because menu is volume rocker down and back is volume rocker up. The new mapping could effect wakeup because the top button is mapped to several different functions ie. short press=menu ......press and hold=keyboard.........hold some more=landscape........while sleeping=wake phone. so thats a lot for one key to do. ideally the top button should just sleep and wake the phone and long press for power off like in winmo. volume does volume. then have the camera button for menu, double click for back and press and hold for a shift/function key ie press and hold camera + left or right key for landscape/screen rotate. the end button should go home when in an app. did i miss anything?
[Touch CDMA General] tatnai:
I'm using new data.img and very fast. I'm using new buttons - yes I've had the wake up issue in some other builds, it was initially introduced with the new button mapping because of the remapping of the power button I think, then vilrod fixed it and I didn't have it with any of his build anymore (I think this fix was in rootfs, pretty sure; it's possible it was in system.img - will look back through the posts to see if I can find what vilrod's final fix was). I still get it with zen and mssmison builds at times. Really intermittent, though.

I now like the new lock screen. I think this build is the "truth". Yeah, still a few force closes/waits, but it rocks.
[Touch CDMA General] zenulator:
I'll look into the force closes. Which apps are they?
[Touch CDMA General] incubus26jc:
i got the new xrom installed last night and installed a few widgets and went to bed with a full charge. screen was off the whole time but my battery was dead when i woke up. Is this normal? or is there any setting i can do to preserve battery power? it shouldnt be dying in 8 hours with no use at all should it?