yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] garringm:
Over the last week I have been running the recent rogers builds over the weekend I was too busy to even plug my phone in after unplugging friday morning. It finally died on me monday morning with low-moderate use, the 10-15 zImage is the one I was using. I have recently moved to the latest zImage and the Magic w/senseUI build posted by Zen. I try tattoo everytime a new build is posted and get the same results I think I am done with tattoo. It boots and runs data connection is 50/50 shot no sounds even with the latest zImage and it likes to hang a lot. I am really liking the magic Senseui build but it still has problems with incoming calls and not recieving them.

p.s. I always keep background data turned on even over this past weekend
[Touch CDMA Android Development] joannerve:
Tattoo and donut builds can t get data connection on Nike
[Touch CDMA Android Development] loserskater:
I was wondering if anybody was working on Tattoo... I'm trying to figure things out but I'm not really getting anywhere. Would anybody like to help me out on getting things going? I know this is a development thread so lets get some ideas going...

Data isn't very friendly so I was wondering where to look to get it more stable.
[Touch CDMA Android Development] zenulator:
what do you need done with tattoo?
[Touch CDMA Android Development] loserskater:
Data doesn't seem to be very reliable.
[Touch CDMA Android Development] bug666:
Tattoo is unusable at this point IMO. Tons of force closes, data randomly cuts out, and it's way too slow. I'd like to use tattoo because of the resolution but at this point it looks like I'm gonna have to stick with cupcake.
[Touch CDMA Android Development] zenulator:
why not donut if you like the resolution?
[Touch CDMA Android Development] plutarcian:
dont know about tattoo (havnt tried it in a while) but hero sure is slow. i think (hope) it should speed up to the point of being usable if it can be made flashable ??? i think reading everything off the sdcard is whts killing it right now.
[Touch CDMA Android Development] 2girls1cup:
what type of sd card do you have? what class
[Touch CDMA Android Development] plutarcian:
8 gb class 4. and i cant seem to partion it. i read somwhere that some cards cant have a second partion ( ???????? ) i.e. if u make one 2gb partition, u will have to forgo the other 6 gb ( in case u were thinking of recommending a swap partition :D )
[Touch CDMA Android Development] ivku:
Did you find solution ? It seems, I have the same behavior.

The problem with data is only in donut/tattoo, in older

builds is data OK.
[Touch CDMA Android Development] tatnai:
a class 6 card may help. also do you have swap set up in hero.user.conf?
[Touch CDMA Android Development] plutarcian:
hmmm. i know class 6 would help but HOW much. i mean will it be REALLY worth it. i have compcache set to 100 and experimenting with swapiness but to date, hero is almost(completely) unusable (unlike ION).
[Touch CDMA Android Development] xxbabiboi228xx:
class 6 will not help all that much i bought one like 2 weeks ago 4gb class 6. I had a 8gb class 4 card and honestly it runs about the same.
[Touch CDMA Android Development] garringm:
Got a question maybe it has been dealt with before but in the virtual memory part of the conf files there are these if I add the values I have posted here I can get hero to run very quick and very responsive, phone lights up on 1st ring in rington kicks in on 2-3 rings ususally in between what do these setting do

vfs_cache_pressure=0 I drop this to zero from 200 that is set as default when downloaded

overcommit_ratio=275 I raise this from the 80 that is set from download

I dont know what these settings do but they make a huge improvement atleast for me. I tried someone elses suggestion about upping the swappiness and it wrecked everything. made it very unusable within the first 10 minutes.

I am using the magic with sense ui build by the way and really like it the only qualm I have is flash is there but is not working can someone fix it

I googled these tweaks and read up on them I seen where a lot of people were setting this cache pressure to 0 on their ubuntu machines but setting the ratio that high shouldn't work over 100% so why does it make a difference for me when I go over the 100 mark

Maybe someone else can confirm what I'm doing maybe its just in my head
[Touch CDMA Android Development] plutarcian:
everytime i think of giving up on hero and going back to ion someone comes along with a suggestion to improve it :). o well ... by the way are you using kaiser or vogue?? and radio rom etc??
[Touch CDMA Android Development] garringm:
Kaiser100/ATT tilt

Radio 1.65.24.36

ROM Solace 3.1

Has anyone tried this yet to either confirm or deny they work as well as I say
[Touch CDMA Android Development] xxbabiboi228xx:
Tattoo

My questions is to you Devs if you can get ion donut running so well why not tattoo its donut as well?

Im trying out the new google ion donut zen posted up right now and my thoughts i think everybody should try it out this thing is flying like a bird that how fast and responsive it is.

I would like to say thanks and congradulate whoever did the graphics and layouts for this it looks very similar to Hero and Tattoo

I know one thing ive noticed that the touch input on the Hero/Tattoo Builds slow the phone down.This Ion donut build and i think Zens Micro hero had the android keyboard and it made things run a little bit faster.
[Touch CDMA Android Development] zenulator:
tattoo is based on a different board and similar but different processor than the vogue and most of it is tied in to htc's proprietary code.
[Touch CDMA Android Development] sshark:
HTC Sense update for Magic....Chinese

http://www.htc.com/tw/SupportViewNews.aspx?dl_id=722&news_id=305

Does this do any good to us?
[Touch CDMA Android Development] zenulator:
We already have the htc sense build. zenmagic but jamezelle is porting the new one now. Hopefully it's faster.
[Touch CDMA Android Development] garringm:
I think a lot of tattoos problem is communication within the os and the hardware. It has a huge problem working with the radio in my device. Its constantly trying to get a signal fix and it works hard doing it this is causing the system to run real crappy
[Touch CDMA Android Development] sshark:
oic, very cool, I did not know zenmagic was magic...which means RIL is/was compatible with our stuff?
[Touch CDMA Android Development] zenulator:
After every thing settles down it's very fast and usable. It's just getting past the initial radio/data lockups. When vilord gets back into it he might have a look into changing around the ril. I can give you guys a build with the htc ril to show how much better it is and how the lockups are ril related. The only thing is data doesn't work with it.
[Touch CDMA Android Development] jamezelle:
man i just realized this dump has the hero bootscreen... wtf:confused:

ill post it if anyone wants it

#
# customize.prop for device
#
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=CUPCAKE
ro.build.display.id=150351
ro.build.version.incremental=70768
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Wed Oct 7 15:04:16 CST 2009
ro.build.date.utc=1254899056
ro.build.type=userdebug
ro.build.user=root
ro.build.host=htcpedia
ro.build.tags=test-keys
ro.product.model=HTC Hero
ro.product.brand=htc_wwe
ro.product.name=htc_hero
ro.product.device=sapphire
ro.product.board=sapphire
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=sapphire
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=2.73.405.38 CL#70768 KiNgxKxROM-release-keys
ro.build.changelist=70768
ro.product.ua=trout
ro.build.fingerprint=htc_asia_wwe_sg/htc_magic/sapphire/sapphire:1.5/CUPCAKE/70768:userdebug/test-keys
keyguard.no_require_sim=1
# end build properties
#
# system.prop for device
#

rild.libpath=/system/lib/libhtc_ril.so
ro.ril.hep = 1
wifi.interface = tiwlan0
ro.ril.htcmaskw1.bitmask = 4294967295
ro.ril.htcmaskw1 = 14449
ro.ril.hsupa.category = 5

# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 300

# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 160
ro.com.google.locationfeatures=1

# For SD storage insert notification sound
persist.service.mount.playsnd = 0

# For auto backlight default value
settings.display.autobacklight=0

# For brightness default value
settings.display.brightness=132

# For the default value of agps
ro.ril.def.agps.mode = 2

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.config.ringtone=Innovation.mp3
ro.config.notification_sound=Color.mp3
ro.config.alarm_sound=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=DISABLED
persist.service.mount.playsnd=0
ro.com.google.clientidbase=android-htc
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
[Touch CDMA Android Development] sshark:
Yea that would be nice! how's radio and data on this?
[Touch CDMA Android Development] zenulator:
The same as zenmagic and other hero builds. it's just an updated sense ui for the hero and now the magic.
[Touch CDMA Android Development] garringm:
Yeah I keep trying but just cant get to that point I think you did this once before and it did prove this fact so at least for me its really not necessary. I am hoping that someone can get the ril right because I would really like to use it with working data
[Touch CDMA Android Development] jamezelle:
yea so i definitely cant get ubuntu to recoagnize my damn phone:mad:, as a drive....

i even tried tinkering with the settings in wm usb to pc and set it to disk drive no go, hard reset, no go....
[Touch CDMA Android Development] zenulator:
I uploaded the taiwan magic sense ui build to vogue-hero. Also dzo put up a new zImage at vogue-android that uses the long press on the camera button to go home so you don't have to set that in spare parts anymore. if your going to use the new zImage i recommend using his rootfs.img also up at vogue-android. I didn't include any extra apps in the new build. The modem and calibrate screen app are in a zip at vogue-hero if you need them.
[Touch CDMA Android Development] sshark:
Nice downloading this one...if I keep all hero apps in androidapps folder it should load them in, right?

I got to play with zenmagic-v1 and found to be pretty nice and responsive. Faster than the hero. Data was reliable and calls and texts were coming through.
[Touch CDMA Android Development] jamezelle:
@ zen: how do i get rid of this: failed to load wifi driver garbage?

IDGAF!!!!!!! i dont even have effin wifi.....
[Touch CDMA Android Development] zenulator:
on what build?? If you're talking about the magic sense build then comment out the wifi lines in the build.prop.
[Touch CDMA Android Development] jamezelle:
yeah that didnt work:(
[Touch CDMA Android Development] pmos69:
overcommit_ratio should only be relevant when overcommit_memory=2

values for overcommit_memory are:

0: heuristic - try never to overcommit

1: always overcommit

2: be precise - commit up to the "Memory allocation limit" (see bellow)

overcommit_ratio = percentage of physical memory size to include in overcommit calculations.

The calculation is like this:

Memory allocation limit = swapspace + physmem * (overcommit_ratio / 100)

swapspace = total size of all swap areas

physmem = size of physical memory in system

setting vfs_cache_pressure=0 does not seem a good idea on a memory constained system. On tipical linux desktop, yes it can make sense, since enough memory is available and using as much cache as possible usually brings good results.

---

but hey: if it works, who am I to disagree. sometimes there are other unforeseen factors and loopholes that influence these things. ;)
[Touch CDMA Android Development] silex:
I still need to try that Ver.3 of Kb7sqi's Zimage and rootfs. Did it get resolved or did we identify that it just doesn't work with Sprint Vogues as of yet? I wanted to mention, but I've been using xRom 1.4r3 and bluetooth works fine for me! Is this not the norm?

By the way, is there a way to stay in Android, use adb to copy over new files and then remount everything? I've just been soft resetting and copying them over via WM. Please tell me there's as easier way...
[Touch CDMA Android Development] zenulator:
bluetooth should work like the ion build in all cupcake non hero builds which is what xROM 1.3/1.4 is. as for the adb file transfer i always. use

adb push system-xxx.sqsh /sdcard/

while still in android.
[Touch CDMA Android Development] jamezelle:
i tried commenting it out in the build.pro no go, then i deleted it in the build prop still not happening.

/OOBE_MainActivity( 1206): startActivityForResult nRequestCode == 1, mnCurStep == 0
V/OOBE_MainActivity( 1206): Customization setup has not run.
I/ActivityManager( 1156): Starting activity: Intent { comp={com.htc.CustomizationSetup/com.htc.CustomizationSetup.SetupActivity} (has extras) }
I/OOBE_MainActivity( 1206): onResume
V/OOBE_WIFIScanAPService( 1206): onCreate
V/OOBE_WIFIScanAPService( 1206): wifi disable
V/OOBE_WIFIScanAPService( 1206): enable WIFI
I/ActivityThread( 1204): Publishing provider user_dictionary: com.android.providers.userdictionary.UserDictionaryProvider
I/OOBE_MainActivity( 1206): onSaveInstanceStateon
I/OOBE_MainActivity( 1206): onPause
I/WindowManager( 1156): Screen status=true, current orientation=1, SensorEnabled=false
I/WindowManager( 1156): needSensorRunningLp, mCurrentAppOrientation =1
I/WindowManager( 1156): needSensorRunningLp, SCREEN_ORIENTATION_PORTRAIT
D/WifiStateTracker( 1156): resetNotificationTimer()
I/ActivityThread( 1204): Publishing provider im: com.android.providers.im.ImProvider
I/ActivityManager( 1156): Start proc com.google.process.gapps for on-hold: pid=1217 uid=10015 gids={3003}
I/SurfaceFlinger( 1156): Boot is finished (55194 ms)
I/WindowManager( 1156): Config changed: { scale=1.0 imsi=0/0 locale=en_US touch=3 key=1/1/2 nav=1 orien=1 }
I/ActivityThread( 1204): Publishing provider com.htc.accounts: com.htc.CustomizationSetup.AccountsProvider
I/PVPlayer( 1132): ------------------- PVPlayer destructor num 1
D/dalvikvm( 1156): GC freed 4224 objects / 178024 bytes in 902ms
E/WifiService( 1156): Failed to load Wi-Fi driver.
I/ActivityThread( 1204): Publishing provider contacts;call_log: com.android.providers.contacts.GoogleContactsProvider
E/WifiService( 1156): Failed to load Wi-Fi driver.
I/ActivityThread( 1217): Publishing provider com.google.settings: com.google.android.providers.settings.GoogleSettingsProvider
I/ActivityThread( 1217): Publishing provider gmail-ls: com.google.android.providers.gmail.MailProvider
E/WifiService( 1156): Failed to load Wi-Fi driver.
E/WifiService( 1156): Failed to load Wi-Fi driver.
E/WifiService( 1156): Failed to load Wi-Fi driver.
E/WifiService( 1156): Failed to load Wi-Fi driver
[Touch CDMA Android Development] silex:
Thanks for the CLI code. Wouldn't the file still need to be renamed? I guess this can be done from the 'adb shell'. And can the /sdcard be unmounted and then remounted in order to relad the new sqsh or is a soft-reset needed still?
[Touch CDMA Android Development] silex:
I verified that "us Sprint Vogue" users are still having issues with v3 of kb7's rootfs and zimage which could possibly be attributed to Verizon using a board panel of 1 and we needing to use 3.

The latest zimage (10/24) and rootfs (10/23) on vogue-android appear to work so far though...
[Touch CDMA Android Development] zenulator:
you still need to soft reset and rename the system file in winmo
[Touch CDMA Android Development] silex:
I was able to boot into system-zenmagic-102309.sqsh using the latest basefiles and kernel files outlined in my prior post. Initial boot took about 20min. Problem is that it runs still pretty slow as opposed to some the other kernels that appear to work with the Verizon version. Hopefully kb7sqi can chime in which his or her thoughts about why us Sprint users get the white screen.
[Touch CDMA Android Development] kdub94:
port request

I was looking at a blur rom (http://xdaforums.com/showthread.php?t=567122). it seems nice and was hoping we could port it to our phones.

Thank you.
[Touch CDMA Android Development] zenulator:
i ran it with dzo's latest kernel and rootfs. maybe dzo can merge what kb7sqi did because it does help with the speed of these builds.
[Touch CDMA Android Development] zenulator:
i did a older version of that. its in depreciated at vogue-hero.
[Touch CDMA Android Development] silex:
Yeah I'm running with dzo's as well, but it's still pretty slow for me. Slow enough that I still need to go back to Ion. In the end it might just be that the micro SD card I have is pretty slow, a Kingston 1GB. Do you guys have a certain program you use to tell you the specs?
[Touch CDMA Android Development] zenulator:
specs of the sdcard? it should say on the package or the card. i'm sure there is a program but i don't use one.
[Touch CDMA Android Development] zenulator:
Damn It now which one do I get?
[Touch CDMA Android Development] jamezelle:
:p it could be worse!
[Touch CDMA Android Development] tallnerd1985:
It's hard to say at the moment because the hardware on the motorola is pretty damn powerful but with HTC, you have the dev community to go along with it. If anything, hopefully the dev community will take an interest with motorola again and come out with some sick mods for the phone. Anywho, we can expect to see the Droid launch Nov 9th and then the HTC Elise and Hero at Verizon.
[Touch CDMA Android Development] jamezelle:
UI

sweet goodness native cdma support for verizon with senseUI:D

oh yea tallnerd vzw still hasnt fixed my data:rolleyes:
[Touch CDMA Android Development] tallnerd1985:
Really, you did ESN change back to your Vogue and re *228 it and it still didn't work?
[Touch CDMA Android Development] jamezelle:
yeah like a week ago, *228 1 doesnt work
[Touch CDMA Android Development] silex:
I started using system-htc-donut.sqsh and it works great! Is it a known issue that the GPS and bluetooth doesn't work?
[Touch CDMA Android Development] tallnerd1985:
WTF! Mine does the same thing right now. I wonder if anybody else here has the same issues with doing a *228. I am using NSFAN's win 6.5 rom with the new touchFLO 2D. If anybody here can attempt doing a *228 option 1 and report back if it work and what rom you're using so we can fix this issue.
[Touch CDMA Android Development] zenulator:
i haven't been able to do a *228 1 after upgrading to nfsfans 6.5....i thought it was because of the sprint hero bug.
[Touch CDMA Android Development] mrkite38:
Ditto - NFSFAN's latest 6.5. Option 2 works, option 1 fails very quickly.
[Touch CDMA Android Development] tatnai:
are you using the CDMA dialer or one of the GSM dialers? uninstall the GSM dialer, install the CDMA dialer (find in his thread) and you should be good to go.
[Touch CDMA Android Development] jamezelle:
oh gosh look what ive started... a

@tatnia i have the cdma dialer diamond themed from nfsfan
[Touch CDMA Android Development] jamezelle:
has anyone been able to port any magic-sense builds besides zen? these library conflicts are making my brain hurt...:eek:
[Touch CDMA Android Development] zenulator:
Try using the libs from my build?
[Touch CDMA Android Development] jamezelle:
i used yours on another magic-sense build and i get the lib errors, what version of squashfs-tools do you have, i have 3.3 maybe that is the problem
[Touch CDMA Android Development] zenulator:
3.4 but that shouldn't make a difference.
[Touch CDMA Android Development] tallnerd1985:
Hey buddy, hold yer horses. I work at a Verizon retail store but from what I know, you are not going to find a rep that can fix your problem because a majority of Verizon employees hate WinMo phones and love their hideous Blackberrys. Today I just started my days off and my wife is letting me toy with my phone to figure out why *228 is not working on our phones. Once I figure this out, I will post a fix for it or what's causing it.

Hey Zen, you might hold out on the Droid, Eris and Hero variant when they come out because Verizon might be getting the HTC Passion which is the CDMA Variant of the HD2 with 1ghz snapdragon Android love.
[Touch CDMA Android Development] mrkite38:
Tell you what - I'll 'guinea pig' back to stock and post results.

Try #1: Flashed back to VZW MR1 WM 6.1, 3.37.78. Still getting the message after 5-6 seconds. Nope.

Try #2: Switch devices on VZW website., wait, switch back. Nope.

Try #3: Hard reset. Nope!

Hope I can find an old phone to use tomorrow! I'll call for a new AKEY... Anyone have anything I should check through EPST or something?
[Touch CDMA Android Development] zenulator:
Unless you want to port 2.6.27 kernel over to our hardware and redo all the progress that dzo and others made we're not going to have that included in our builds and taken from the ubifs site "One thing people have to understand when dealing with UBIFS is that UBIFS is very different to any traditional file system - it does not work on top of block devices (like hard drives, MMC/SD cards, USB flash drives, SSDs, etc). UBIFS was designed to work on top of raw flash, which has nothing to do with block devices. This is why UBIFS does not work on MMC cards and the like - they look like block devices to the outside world because they implement FTL (Flash Translation Layer) support in hardware, which simply speaking emulates a block device on top of the built-in raw flash. Please, make sure you understand the differences between raw flash and, say, MMC flash before dealing with UBIFS.S" so this isn't going to help.

If you want compcache you'll need at least a 2.6.29 kernel so you can also support backing swap. So aside from somebody porting the 2.6.29 kernel and using compcache or HTC releasing a more optimized sense ui or building a flashable image this is the best that hero is going to get for now. I've heard from people that run hero on the dream that this is almost as fast. I've read in the hero forums that people were complaining about it being slow on a real hero. So the only things I can do now is take parts out and replace them with optimized ones or leave parts out all together so that more memory is dedicated to the core system.
[Touch CDMA Android Development] jamezelle:
hey, this latest 8-15 build is very fast and stable thanks alot zenulator! great job!:cool:
[Touch CDMA Android Development] mssmison:
compcache is not even really going to speed it up, there's alot of back and forth about it but basically a swap file is just as good. Zen's right, everyone needs to accept that the hero builds are just going to be slow. He's done great work thus far.
[Touch CDMA Android Development] ljinsane:
WHAT!?!:confused:

I said in a thread yesterday and previous to that, that wifi was working in a here build..specifically zen-hero-090809. I guess nobody noticed that.:cool:

So all this time you have been working on the hero build you have purposely not been including wifi?

Please make a build including that. Your latest test build works great sms,speed, calls, data and gps with wifi I ( and I'm sure others) could use this daily.

my 2 cents
[Touch CDMA Android Development] mattcoz:
Ok, I must be blind or something, because I can't find any settings like that. :confused:
[Touch CDMA Android Development] NarSan:
I can upload for you bundle with working wifi (or only system.img)

edit:

sorry, build is from enatefox, but wifi is working and I can upload files