yashsingh1/xdaforums huggingface dataset:
[Touch Diamond2, Pure Android Development] vyis:
Hmm,don't understand, but in my case the device will wake up without tapping on the screen in around 1-2s. Below is my current startup file.

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 2293

set KERNEL zImage

set initrd initrd.gz

set cmdline "lcd.density=240 msmvkeyb_toggle=off rel_path=root/Android sensor=topaz pm.sleep_mode=1 acpuclock.oc_freq_khz=614400 htc_hw.call_vol=5 htc_hw.handsfree=1 htc_battery_smem.fake=1"

boot
[Touch Diamond2, Pure Android Development] hugulugu:
this configuration of the startup file works very nice on my device :)
[Touch Diamond2, Pure Android Development] chiuzw:
My device is MDA Compact V (HTC TD2). I tried the FRX07 on my device, because I can't do the touchscreen calibration when first boot, so I use old kernel (1231). It can enter android system and create ts-calibration file.

I go back to recent kernel (1342, 1346), but it always stops after the touchscreen calibration. I also tried to rootfs with latest rootfs, but the problem is exist. From the screen, I can see the last messages are:

[54.941894] touch_calibration: Point 1 141, 920.

[54.941894] touch_calibration: Point 2 865, 922.

[54.941894] touch_calibration: Point 3 513, 559.

[54.941894] touch_calibration: Point 4 147, 196.

[54.941894] touch_calibration: Point 5 872, 190.

[54.941894] touch_calibration: do calibration ok.

[54.941894] touch_calibration: x max 89, x min 924.

[54.941894] touch_calibration: y max 144, y min 977.

[54.941894] touch_calibration: x reversed, y same direction.

I wait about 30 mins, but there is nothing to do. If I change the kernel to 1231 again, it can boot into android system.

The old kernel (1231) is not stable, my device sometimes reboots automatically, so I want to use latest kernel.

Is any solution for my problem? Thanks.
[Touch Diamond2, Pure Android Development] arrrghhh:
So even with the "generic" ts-calibration file from the first post, Android fails to boot? Have you tried with a new data.img?

That's an odd one. I'd be curious is adb was up so you could pull logs, I think there's something more going on than just calibration problems...
[Touch Diamond2, Pure Android Development] chiuzw:
I tried the ts-calibration which is from the first post, and tried to delete original data.img to force create a new one, but the Android still fails to boot. The problems are the same.

I will try to capture the logs from adb, thanks.
[Touch Diamond2, Pure Android Development] arrrghhh:
Just to be sure you're replacing the kernel correctly, please look over the Incremental Updates page.
[Touch Diamond2, Pure Android Development] vyis:
Just curious, can we just replace the kernel without delete data.img?
[Touch Diamond2, Pure Android Development] arrrghhh:
Yup, not a problem. Most things you can replace without removing the data.img, it's only if things go horribly wrong that you should be blasting out that file.
[Touch Diamond2, Pure Android Development] bibiteri:
new kernel 20110819
[Touch Diamond2, Pure Android Development] arrrghhh:
Yes, the LED changes have been merged mainline. So you can now change the behavior of the sleep LED - you can actually use it for notifications now ;).

It seems the default is now 0, which seems like a really bad idea to me.

Edit - This post covers the stuff you need to change to adjust the values for enabling/disabling notifications. This post covers the userland lib so the LED will actually blink.
[Touch Diamond2, Pure Android Development] detule:
Arrrghhh, Starfox's testing kernel is using an earlier incarnation of the LED patch, and those instructions are no longer completely relevant. Up to date instructions, and also an app for switching modes on the fly, can be found in this post.

Thanks for spreading the word.
[Touch Diamond2, Pure Android Development] arrrghhh:
Thanks for making that clear dude. I didn't realize that changed so...
[Touch Diamond2, Pure Android Development] rhs013232:
I am using the htc-msm-linux @ 20110819_183957 and rootfs-20110816-7e04198.zip

Start from enter android, it doesn't have any network and I cannot enter the call setting page. Once I try to enter it, it just have a black screen and return to the previous page.

Also I cannot enter messaging, it just show black screen and ask me to force close after a while.

And also can I change the wake up key from windows button to the power button?

Thanks for help!!
[Touch Diamond2, Pure Android Development] 1edge1:
I have the same setup on my topaz and everything works great. There might be a problem with ur startup file or your windows mobile rom. Which rom are you using?And has it worked properly before using the above kernal. Try a different kernal
[Touch Diamond2, Pure Android Development] 1edge1:
How do u change the blink LED color from amber to green?

Thanks for your help and advice
[Touch Diamond2, Pure Android Development] rhs013232:
I am using Energy rom. It worked normal when I used FX06, but start from FX07, it auto restart when entering android untill I use this setup. Any suggestion of the kernal?
[Touch Diamond2, Pure Android Development] 1edge1:
I use the 4 July energy rom, dinik glass version. Not the standard WinMo version. Then I run the latest the roofts etc with the htc-msm-linux @ 20110711_082424 works like a charm. Most stable boot and running time I had experienced. I Use the Frx07. Recently started using the htc-msm-linux @ 20110819_183957 kernal and it boots fine too. Maybe ur data.img file is corrupt. Try a different kernal first before trying anything else.
[Touch Diamond2, Pure Android Development] rhs013232:
IC, thanks a lot! I try different kernal then.
[Touch Diamond2, Pure Android Development] detule:
I have a different device from you, but I am seeing a blinking amber only when the battery is critically low. Can you make sure you have a full charge before disconnecting and sending yourself an email/text message to test what color the led blinks with?

If you are still seeing blinking amber post a "logcat -v time" as well as a "dmesg" covering the period before and after receiving the notification (the app GetLogs works great for this.)
[Touch Diamond2, Pure Android Development] Frank67:
I copied the Zip archive from the first post to the root of the SD Card plus copied

startup.txt from STARTUP/Topas to the SD root....

then i copied the latest kernel 20110819 to the root folder of the SD card ..

after starting Haret it takes appr. 2 min and it is running loops between xdandroid animation and unlock screen...
[Touch Diamond2, Pure Android Development] 1edge1:
I got it to work, It was the actual program that had the problem. Thanks for the help though. I am struggling to make it blink though. I can upload my .conf file if it will help
[Touch Diamond2, Pure Android Development] arrrghhh:
Odd. Did it create a data.img? Have you simply tried rebooting? Did you replace the kernel per Incremental Updates? If a simple reboot doesn't fix it, and you feel you've followed the replacement steps correctly, delete the data.img and try try again.

You need to have the bind mount statement on its own line, like I have below:

# custom shell commands, these commands run last
custom_shells{
chmod 777 /etc/dbus.conf
#echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
rm -f /sdcard/fsck*.rec
mount --bind/sdcard/lights.msm7k.so /system/lib/hw/lights.msm7k.so
modprobe ipv6
modprobe xt_owner
modprobe ipt_REJECT
#echo "Hello!!!" echo # example
# "You can create your own commands here" # example
}

You had it jumbled in with an echo line, and if there's a hash at the beginning ("#") that means the line is commented out - as in it won't get processed, those commands won't get run.
[Touch Diamond2, Pure Android Development] 1edge1:
I tried that and still no luck. Still a solid green light. I currently looks like this:
[Touch Diamond2, Pure Android Development] arrrghhh:
Crap, I shouldn't answer questions on forums right after I wake up.

You're missing a space between --bind and /sdcard. See the "fix":

# custom shell commands, these commands run last
custom_shells{
chmod 777 /etc/dbus.conf
#echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
rm -f /sdcard/fsck*.rec

mount --bind /sdcard/lights.msm7k.so /system/lib/hw/lights.msm7k.so modprobe ipv6
modprobe xt_owner
modprobe ipt_REJECT
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
}

Assuming the lights.msm7k file is in the right location (root of SD, no folders) it should now work :p. Sorry 'bout that.
[Touch Diamond2, Pure Android Development] 1edge1:
Thanks for replying so swiftly. I tried that by making a space and still no luck. My lights.msm7k is in the root of the sdcard(no folders) and my .conf looks like yours. What am I doing wrong?
[Touch Diamond2, Pure Android Development] arrrghhh:
I guess do an md5 check. md5sum /system/lib/hw/lights.msm7k.so, then md5sum /sdcard/lights.msm7k.so and see if they match.

I just noticed I put a modprobe command at the end of the bind mount... Not having a good day today!

mount --bind /sdcard/lights.msm7k.so /system/lib/hw/lights.msm7k.so

Is the line you should have, all by itself. I'm not sure why I can't seem to provide a good user.conf today, ugh. Sorry.

# custom shell commands, these commands run last
custom_shells{
chmod 777 /etc/dbus.conf
#echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
rm -f /sdcard/fsck*.rec
mount --bind /sdcard/lights.msm7k.so /system/lib/hw/lights.msm7k.so
modprobe ipv6
modprobe xt_owner
modprobe ipt_REJECT
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
}

It also sounds crazy, but make sure there's one 'extra' line after the last brace }. So there should be an extra 'empty' line after the last brace... The code above doesn't really relay that properly, and I noticed without that extra line the user.conf isn't processed correctly...
[Touch Diamond2, Pure Android Development] 1edge1:
That did the trick. Third time is the charm. It works. I have no idea what a md5 check is though. Good thing it didn't come to that. Thanks a lot for ur help. Also I noticed that the .conf file keeps becoming 0bytes after each restart of the phone instead of its actual 200bytes. I jsut want to make sure that's normal.
[Touch Diamond2, Pure Android Development] arrrghhh:
0 bytes is not normal. That would indicate the file is empty, which it shouldn't be.

Do you have issues booting again after it goes to 0b?
[Touch Diamond2, Pure Android Development] 1edge1:
Nope it boots fine everytime. No problem. Must be a windows glitch then. Thanx again. Save so much battery without the LED being on all the time.
[Touch Diamond2, Pure Android Development] arrrghhh:
lol, you won't notice a boon on battery life... LED's take up such little in the way of battery.

The real benefit is actual notifications about charging, text messages, etc.

Glad it's workin now for you tho ;).
[Touch Diamond2, Pure Android Development] Black.Heart:
Better android...

Hello XDAndroid devs and specially arrrghhh. I use FRX07 and i'm really satisfied with it... The most stable build I ever used. And with the last kernel (08.19) I even use it instead of WinMo. But I don't understand why XDAndroid devs don't develop .35 kernel? It does have the potential of being the best kernel for Topaz and Rhodium. It doesn't have the sleep issue and wakes up really fast. The last .27 kernel is good and I love it because of fixing that annoying LED debugging mode. But's it's really slow and I can say it's the slowest kernel I ever used. I'd love to see a nice .35 kernel for our devices. Since I don't have the necessary knowledge of developing open source (yet!), I can only wait to use other dev's work :(
[Touch Diamond2, Pure Android Development] arrrghhh:
Did you look around?

There's a .35 autobuild and a .39 autobuild.

Eventually all kernel devs will move to .35. It's gotta happen at some point, but it'll be a little while before all devices can run .35, stably.

Plus, .35/.39 have the new acoustic stuff baked in, so you'll need the new acoustic libs.
[Touch Diamond2, Pure Android Development] Black.Heart:
Yes, I looked around and I was aware of these kernels :) I was saying why devs don't develop these kernels instead of old ones.
[Touch Diamond2, Pure Android Development] arrrghhh:
They're developing both in tandem. No clue why you're thinking that .35 development isn't happening...
[Touch Diamond2, Pure Android Development] Black.Heart:
Because it's getting updated rarely and I didn't see any comments about it. :)
[Touch Diamond2, Pure Android Development] arrrghhh:
That's... nice.
[Touch Diamond2, Pure Android Development] detule:
I am no expert but the cutting edge development right now in terms of kernels for our devices is in fact happening in the .35 trees for topaz and kovsky. In fact, the LED changes to .27 are only a backport of ideas emwe and Alex had already in place in their .35 trees. Count yourself fortunate that the main .35 effort seems to include topaz right now (more so than say rhodium).

Alas, as with most advancements, it's not a smooth progression and I think the newer kernels are seeing some of this. While .35 and .39 both seem to improve the way our devices behave in certain aspects, they seem to break other things on our phones.

Finally, while wince "developers" porting android seems like a mythical group of people, they are in fact only human, and only a few of them at that. They all take vacations, have jobs in real life, and most of all, have the freedom to pick the projects that interest them. It is the nature of things, and I think it's best to come to terms with the situation right now: many people that have the know-how to develop for our phones have moved on to other devices, and more will with each passing week. I would temper my expectations and not even hope for a stable release of a post .27 kernel that would work across all legacy devices that the current kernel supports.

The moral of the story is, if you want something done, it's best you start staring at the git trees and trying to learn low level C.
[Touch Diamond2, Pure Android Development] Black.Heart:
Thanks for informing me. I'd like to learn open source, but currently as you said, I have my own life and university takes a lot of time from me... I know C++ well but not C. And I started to learn C# these days. I'm familiar with linux and stuff but i'm not an expert. I'm just a new learner of the world of open source... Thank you again and arrrghhh don't get mad at me, I have no offense to anyone :)
[Touch Diamond2, Pure Android Development] arrrghhh:
So long as you (or anyone else) doesn't act like they know what the devs should be working on, we're good.

You started with quite an attitude, as if you knew what devs should be working on, and acted like they're stupid for working on .27. Not cool.

Developers will work on what they see fit. You can try to ask them nicely if you have a pet peeve, but it's usually best to just fix it yourself if you really have something that's nagging. Welcome to the world of Open Source.
[Touch Diamond2, Pure Android Development] Black.Heart:
I completely agree with you mate. I'm a dev too and I don't like someone to tell me what to do. So yeah, I don't do it to other devs at the way back :) I was just asking why .35 kernel is getting developed slow... I thought devs are focusing on .27 and left .35 into dust for now. When you said it's getting developed I got warm in heart :D
[Touch Diamond2, Pure Android Development] Black.Heart:
And now, a related question: Why GBX0A is facing problems with textures? Is there any ways to fix it? Like 3D drivers or something?
[Touch Diamond2, Pure Android Development] arrrghhh:
Please post GB related questions in the GB thread.

I don't know what you're talking bout tho, the only issues I had in GB was NeoCore. Everything else worked fine.
[Touch Diamond2, Pure Android Development] Black.Heart:
Same. I thought it has issues with all 3D apps... But it seems it's only facing problems with NeoCore.
[Touch Diamond2, Pure Android Development] pcbilski:
Firstly let me start off by saying, LOVE your work!

So awesome to be able to run 'droid on my Topaz, but kind of makes me want a proper 'droid phone even more. Will have to wait until next year for my upgrade. :(

Now, a question or 2 if I may.

I am using the latest build and kernel and manage to boot into Android 100% however there is a non-functioning keyboard on the top right of my screen, covering about a tenth of it, makes it very difficult to use as it covers some important stuff.

Any tips on getting rid of it?

Guess thats the only query I have for now.

Sorry if this has been answered elsewhere, I did look through as much as possible but didn't find anything.

Thanks in advance.
[Touch Diamond2, Pure Android Development] arrrghhh:
Do you have this line in your startup.txt?

msmvkeyb_toggle=off

You should use the Topaz startup.txt file that's included in the bundle. Paste your startup if you have questions.
[Touch Diamond2, Pure Android Development] pcbilski:
Hi. Thanks for your reply, my startup file is as follows:

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 2293

set KERNEL zImage

set initrd initrd.gz

set cmdline rel_path=FRX07 "lcd.density=240 msmvkeyb_toggle=off sensor=topaz pm.sleep_mode=1"

boot
[Touch Diamond2, Pure Android Development] arrrghhh:
Ah. See my fix above. Need to put everything in the cmdline between quotes ;).

I'm honestly surprised it booted at all! I guess it just picked up the rel_path value and ignored everything else... heh.
[Touch Diamond2, Pure Android Development] pcbilski:
Ah ha! Awesome, thanks so much!
[Touch Diamond2, Pure Android Development] Black.Heart:
FRX problem

I'm facing a problem with FRX since FRX06 I think... The problem is I can't install some apps but sometimes they will install :confused: apps like Firefox, Angry Birds Lite and iKamasutra (:D) I don't know what is the problem... I don't have this issue on GBX. They will install via AndroidApps folder, but not directly from Android and apk file.
[Touch Diamond2, Pure Android Development] arrrghhh:
Well those apps probably require different architecture. For example, Firefox requires ARMV7. Our chipset only supports V6...

No clue about the other apps, but could be something related..?

I know certain apps that required the secure store on the SD card wouldn't install correctly on release of FRX07. Updated rootfs resolved that issue.
[Touch Diamond2, Pure Android Development] cukierkas:
Hello guys. Tired of waiting :)

Just another week bought brand new galaxy ace, upgraded fw to 2.3.3 and rooted.

happy with that. Was thinking to buy galaxy s1, but ace is cheaper and doing the same. the only and main con: small battery :(

diamond was short, galaxy ace is even shorter :(
[Touch Diamond2, Pure Android Development] arrrghhh:
Hey guys, updated to FRX07.1 maintenance release. Some outlying bugs fixed, and the build is completely up-to-date. See the changelog for details!
[Touch Diamond2, Pure Android Development] pgriffith:
Awesome update, seems to be the best build I've tried so far.

Thanks
[Touch Diamond2, Pure Android Development] Ryan_:
Thanks arrrghhh! What kernel you used? 20110819_183957?
[Touch Diamond2, Pure Android Development] metho88:
Hi arrrghhh, thanks for the new update. For the installed apps and settings I made in FRX07, can I use them in this update? is it ok to copy the file data.img form FRX07 and paste it in FRX07.1? or I have to re-install them.
[Touch Diamond2, Pure Android Development] Ryan_:
You can copy the data.img metho88. I always do this and never had any problems.
[Touch Diamond2, Pure Android Development] metho88:
Thank you Ryan_ for your help, I will try :)
[Touch Diamond2, Pure Android Development] arrrghhh:
Please read the first post.

Yes, like Ryan_ said you will be fine copying the data.img over.
[Touch Diamond2, Pure Android Development] bigheadlyf:
Nice update! I like the LED control in new kernel.

Any news of the incoming call issue for Topaz? :)
[Touch Diamond2, Pure Android Development] arrrghhh:
Until a dev with a TOPA fixes the issue, it won't get resolved. It's unfortunately a TOPA-specific bug, and there's only one dev that I know of with a TOPA. He traced the issue for weeks and still was unable to track it down...

So until someone steps up to fix it, the bug'll never get fixed. Sorry... C'est la vie.
[Touch Diamond2, Pure Android Development] bazookadude:
at first: THANK YOU FOR THE HARD WORK.

i must wait until the end of november before i can get me a real android phone so until then i have to use this one.

now to my problems:

when i strat op haret, it starts booting android.

android starts, and i unlock the screen.

immediatly i get the message:

"unfortunatly the process android.proces.media has stopt. try again."

i press close and make the first call.

next issue:

market doesnt work it wont download anyting stuck at starting download.

next issue:

facebook wont start i get the message:

"unfortunatly the process android.proces.media has stopt. try again."

whatsapp works fine,

google maps works fine to,

thanks for the hard work, it is much appreciated
[Touch Diamond2, Pure Android Development] latinohot:
should wait after booting to android

give it at least 5 min, i usually let it sit for 10 minutes before i do anything after first boot
[Touch Diamond2, Pure Android Development] bazookadude:
i have tryed this but still no change.:confused:
[Touch Diamond2, Pure Android Development] arrrghhh:
Just hit force close. They go away. Like latinohot said, on the first boot you must let it settle. 10 minutes is not an exaggeration either. Let it sit for 10 minutes AFTER you see the lock screen.

Still FC fest? Delete the data.img, and try the whole process again.
[Touch Diamond2, Pure Android Development] manpiu23:
This maintenance bundle works great. I would say the biggest shortcoming is battery. Then a few freezes here and there. If the battery usage can b improved then we may not even need the NAND. Good job devs.
[Touch Diamond2, Pure Android Development] jones23:
How much battery life do you get out of FRX07.1 ?

With the maintenance release I get only 3 hrs with wifi and GPS off.

With the older Bundle FRX06 I could easily get 10 -12 hrs out of the battery (also with wifi and GPS of).

Maybe I need to do a new setup.
[Touch Diamond2, Pure Android Development] metho88:
Guys, for the incoming call issue, I'm not sure if it's the one I had, the system is freezing and reboots itself once it faces an incoming call. I have noticed this issue with the last couple of kernels. But when going back to the one dated on 16 Augest, it rocks. The issue dissappears. :)

Ok, my problem is when I want to end a call, I press the (end call button) but instead of ending the call, it takes me to the home screen even after selecting the -Power button ends call- option in Accessibilty settings. :(

Is there any way, like adding someting in the startup.txt. I dont want to look for any more apps. :(

Thanks in advanced.
[Touch Diamond2, Pure Android Development] arrrghhh:
If anything, you should be getting better battery life.

Read the changelog, there's a suggestion on how to debug sleep. Make sure your phone is sleeping properly.

There isn't a kernel from 8/16...? :confused: Even going back to 2010...

At any rate, the end key is now home. You can remap the power button to end calls thru the "Accessibility" menu. With the new in-call menu, there's no longer a need for a hard button to end calls - and there's a pretty good case to have a dedicated home button.
[Touch Diamond2, Pure Android Development] Rosya:
no sound at all

hii guys ... i'm very very new to this ... but i downloaded the bundle and run hart and everything running smoothly ... but i noticed one big issue ,,, i have no sound at all ... no ringtone no notification and no incall sound even i receive calls and make calls and receiving sms normaly .. but no voice at all i cant hear the caller and the caller cant hear me .. and when i try to set a ringtone i got error that not responding and 2 chooses 1- force close ..2-wait ,,, if i waited nothing happens

so i forve close .. but everything else runs BT and WIFI and surfing the internet