yashsingh1/xdaforums huggingface dataset:
[Click Android Development] andynroid:
Thethering is ready in NB160

SentFromMyHTC_Tattoo=NB160
[Click Android Development] baltahakki:
err im not installing nightbuilds because of crashes and bugs etc. and actually its been a long time since the last stable release..

so is there any stable version release soon?

Thanks.
[Click Android Development] Vieira:
I did have the same problem with the video camera and a full wipe does indeed solve the problem.

About the battery before the full wipe it drained quickly (it was half way when I went to bed and I had no battery when I woke up). I did a full wipe and recharged. I will report back.

BTW, arco thanks for this new kernel. Amazing job! I had already lost any hope of seeing a new kernel running on click.
[Click Android Development] andynroid:
I did the same too no issues so far and have been flashing the NB on daily basis

SentFromMyHTC_Tattoo=NB160
[Click Android Development] andynroid:
Kalim n arco are the masters of these creations trust me the NB are stable as I flash them on daiy basis...

SentFromMyHTC_Tattoo=NB160
[Click Android Development] lukic:
I am on the NB 159 with a new kernel and I have a calibration problem. I can't properly calibrate my screen. I was using Tattoo Calibrate app before, but it is not working any longer. Now, I can't choose any custom string, the default one remains no matter what I do. It's really hard to type messages now, for everything else it's usable. Could you fix that problem Kalim?

Except this issue, ROM is super fast and stable, much better than any older versions. Kudos to Kalim and Arco!
[Click Android Development] andynroid:
Is the error stated 'invalid cal...' as I am getting this just realized it as my top right corner no longer works on contact coz I have dropped this device over 10 times.

Other points are ok...FYI

SentFromMyHTC_Tattoo=NB160
[Click Android Development] lukic:
You are talking about HTC Calibrate app, and I was talking about Tattoo Calibration app.

I have tried that one too, and calibration was successful but it still not good when I use it.

To use Tattoo Calibration app you have to download it and install it manually, it doesn't come with this ROM. You can get it here: http://www.box.net/shared/ymsoke5ety
[Click Android Development] rikkardino:
Arco you are right , of course !!! The battery now is working as before and the videocamera as well ;finally. About the videocamera what I did was install an old version rom (cm 7.1.0 t5 ,that I consider more stable) and then install the new NB160 "et voila'" now is working perfect.

Just a question with the new kernel could be possible to develop Flash app. working on our Tattoo, or remain it a dream ?

Special thanks to you.
[Click Android Development] KalimochoAz:
Flash is a dream since is no compilation for our processor. There are 2 ways, or someone builds a new version for all processors ( not probable since there is not a big amount of this processors in the market and working ) or we decompile/dissassamble the package with IDA and rebuild with our processor instructions, that is more than a dream ilegal.

So at this moment I'm not so confident with this topic.
[Click Android Development] KalimochoAz:
lukic, what is the probem with HTC Calibrate? Can you send me logs and the calibration points you get after using HTC Calibrate? Use Touch Test in order to see how good/bad is your screen calibrated
[Click Android Development] rikkardino:
but..HTC Wildfire(Buzz), use the same processor Armv6 -Qualcomm® MSM7225™, 528 MHz and I installed a Flash app. working good and I see another Flash app. especially for armv6 processor(XDA) but with my Tattoo the browser always crash !?
[Click Android Development] lukic:
HTC Calibrate sometimes work and sometimes it gives me Invalid calibration error.

But even when it works and calibration is successful, noting is changing. It is still not good.

Here is a log:

Default calibration string for this ROM is now:

836,878,202,884,512,520,837,121,204,121

but on my screen proper value should be:

855,905,173,905,515,507,855,110,173,110

I was always using Tattoo Calibration app to fix this but now it doesn't want to change it. So I am pressing SPACE key on the keyboard all the time when I type, and it is very annoying.

This is log from Tattoo Calibration app:
[Click Android Development] lukic:
I did a clean install and HTC Calibrate seems to work fine now.

Thanks Kalim ;)
[Click Android Development] nikson346:
Sorrry. didn't read the thread. please delete the post.
[Click Android Development] theslime:
This has happened to me once on CM7 (7.0 and 7.1RC), but interestingly it's happened SEVERAL times (as in at least five, probably more) on stock Sense/Donut. One time I was an hour late to an important meeting, and another time a whole switchboard service had to close down because my phone didn't wake me up in time for my shift. Thankfully, both bosses forgave me. :)

Since it happened more times on stock than on CM, I think we can rule out CM as the culprit. I didn't use any task killers either, and it failed with more than one launcher (Sense on stock, ADW on stock, ADW on CM, and GO on CM), so I don't think that it's that either.

I don't know anything about these things, but my guess is that the alarm wouldn't have gone off in these cases where the unlock screen shows the wrong time, although I could be wrong. I think it's the same thing.

Interesting. I'll try this. Sometimes, my phone automatically sets itself just after I unlock it, though. Does that fit with your explanation? That's not a rhetorical question, btw. :)

But now my problem is this: right now I don't trust my phone to act as a proper alarm clock. It's worked 95 times out of a 100, or maybe more like 99 with CM - but that's still 2 days that could potentially cost me my job. I'd like to use my phone (I like the Gentle Alarm app) instead of my annoying standalone alarm clock, but I just don't trust it enough. I'll change to manual time, and then hopefully, if I don't see the wrong time at unlock pattern screen again for a few months, I'll start trusting it again. :)
[Click Android Development] theslime:
This might be a good opportunity to express my thanks to KalimochoAz and Arco and the other people who made this happen. You've saved my piece of s**t phone with an obsolete OS and turned it into something great, and I'm really thankful. Now it even has a proper and new kernel. Impressive to see that the great work continues on such an old phone.
[Click Android Development] zxcv321:
I install nb159,nb160, before install nightly build, I do factory reset before go to recovery,then go to recovery ,wipe cache, format system, then choose zip install,reboot.

then open camera, switch to video record.

something it works fine for longer then six minutes, sometime it fail, I don't know how to avoid camera from crash, it happen unexpected. attachment is logcat, when I start camera, start preview, then I switch to video record, it crash immediately, then force close camera, start again, now it says cannot connect to camera. logcat record all what happened yet. thanks for help!
[Click Android Development] KalimochoAz:
Go to recovery:

Do factory reset

Do clean cache

Install NB160

Restart: ( don not recover any backup )

Try camera to see if this still happends please
[Click Android Development] strangre:
Any body having signal reception issues in tattoo.. I am now in india..I've checked several mobile carriers and my tattoo is getting weak signal.. same place my nokia mobile is showing full signal strength..any fix for this issue.. I'm using CM NB 2.3.5
[Click Android Development] KalimochoAz:
What NB are you using?
[Click Android Development] KalimochoAz:
Do you remember when HTC told us that Tattoo is not going to be upgraded to 2.x because of the speed of the terminal?
[Click Android Development] sunitknandi:
Yes I remember. U proved them wrong! :D
[Click Android Development] Vieira:
Yes I do! And then people got it running... and then the camera took pictures, and then we got the previews, video and FM radio.

Thank you (and arco!) for all your hard work (and I suppose it was a lot!) and effort. If it wasn't you, we would still be running 1.6...
[Click Android Development] KalimochoAz:
We all proved they lie, is not only my work. Arco played this game fully clear, never bad words, never more than work and work and work. Team play is alway a winner, and if you have Arco in your team, better
[Click Android Development] sanderd17:
Oh yes I remember. And I also remembered the moment that I looked back at the XDA forum and saw a very active thread about someone that got some raw images from the camera.

BTW, I'm now testing the video camera with NB 161, no crashes so far for a record of 6 minutes. I will logcat every time I run the camera, so if it crashes, you'll hear of it.
[Click Android Development] sanderd17:
BTW Kalim, where is the camera app code hosted (not the driver but the app)?

I would like it to keep recording while the screen is off (if that is possible), so I guess I would have to change the mapping of the red-phone key in the camera app.

That way it will be a camera logger. Just logging every image where the phone goes.

It works with the screen on, but it uses a lot more battery.
[Click Android Development] sanderd17:
Sorry, it just crashed again. It seems to crash a lot faster when the memory or the processor is used more. So this time, it was again with a GPS log app running.

It's just like the camera app isn't able to keep up with the movin image and blocks. Do you think it would be worth to try it on the lowest resolution?

Here is the logcat: http://pastebin.com/w9S3rvhH
[Click Android Development] goran95:
Kalimocho,do you make some new release?? :-) :-)
[Click Android Development] zxcv321:
Install it again use the order above, camera works well at begin, then I use titanbackup to restore my app, when all done, I start camera and switch video record, it crash again, screen picture in picture, and then show fc dialog.
[Click Android Development] strangre:
I'm using NB 155
[Click Android Development] KalimochoAz:
http://download.cyanogenmod.com/get/cm_click_full-162.zip

Is Nightbuild 162. Is stable and for me is a daily ROM, so please change to it.

I will do the next official Release as soon as other devices are correct and cyanogen decide to make the official next release, but belive me that you can use the NB.
[Click Android Development] sanderd17:
Mine also crashed without restoring a titinium backup. So the problem is still there.

Apart from that video recording issue, the ROM is just perfect. A lot better than I ever had expected from Tattoo hardware.
[Click Android Development] Fredericosilva:
NB160 is 2.3.5?
[Click Android Development] andynroid:
Yup!

SentFromMyHTC_Tattoo=NB160
[Click Android Development] Fredericosilva:
and between nb160 and nFinityGB witch is better? witch has better performance?
[Click Android Development] mitsakhs:
just tryed

http://xdaforums.com/showthread.php?t=1111145

and works pretty well with nb 162 i have much more free ram
[Click Android Development] sanderd17:
It didn't crash my phone, so let's see if it is better in the long run.
[Click Android Development] Lazdaa:
Hey guys just installed this rom, but when i first turned on my phone there were no status bar.. and its still not there..

Help anyone
[Click Android Development] Lazdaa:
Uhm did i get this right?.

Is the 160 stable or the 162?

And btw i can't dl the 162, it stops at 99% or some like that...
[Click Android Development] KalimochoAz:
Try again with 162
[Click Android Development] sTiCkY88:
oh nvm i found it lol
[Click Android Development] sanderd17:
I tried filming again, it crashed agian, but I didn't bother to reboot my phone. Now, a few hours later, I notice that it drained my battery and that my phone feels quite hot. If that could help anyone with diagnostics.

Oh, and btw, I don't feel a real difference (speed wise) with the RAM script, but it's certainly not worse.

@Lazdaa, can you check the ADW settings?
[Click Android Development] Lazdaa:
Well i've fixed the status bar thingy.

But now my market just seem buggy, with lags and force closes..

Anyone else having this issue?
[Click Android Development] potattoo:
i flashed nb162 but got several reboots. so i wiped dalvik & cache and flashed it again, but then got infinite tattoo logo screen.

so i tried to restore my last backup i just made before flashing but it says 'MD5 mismatch!' :mad:

then i installed RC1 over it again, but its was also misbehaveing.

so now i wiped and installed nb162 and it seems to work so far...

is 2.3.5/nb162 not allowed to be install over 2.3.4 without wipe?
[Click Android Development] KalimochoAz:
Is better to make a clean install. It could work without, but...
[Click Android Development] LionGreen:
I have N163, but unfortunately these nightbuild is spending to much my battery :(

Witch nightbuild is better?
[Click Android Development] sanderd17:
Try changing the CPU governor in the Cyanogen settings to "ondemand" or even "powersave".
[Click Android Development] andynroid:
I wonder no more changelog in the NB?

SentFromMyHTC_Tattoo=NB161
[Click Android Development] Hanisa:
it seems there aren't any update.
[Click Android Development] lupp0l0:
With nb162 I have a weird problem: when charging battery at night, the charge reach 100% and then start discharging. When I wake up and unplug the phone the battery indicator drop to about 50%. Anyone else? Maybe it's a coincidence and my battery dead exactly after flashing nb162?
[Click Android Development] potattoo:
Help please! First big problem here: if i make a nandroid backup and then try to restore it i allways get 'md5 missmatch' :eek:

Next big Problem: since updateing to nb162 i have reboots all the time. It doesnt go to Tattoo boot logo, but immediately shows the CM7 boot animation. After loading up and entering my PIN it takes a minute or so and then reboots again :eek:

EDIT: well at first it did work well (after the clean install) then i restored my Titanium Backedup apps. Maybe some app fails on 2.3.5 or vice versa?

ADW launcher also doesnt respond.

Im useing default values for CPU (which did work before)

Please help me fix my tattoo!
[Click Android Development] andynroid:
The battery readings are incorrect since the new kernel...I would say eg. at 20% goes to green happened today...

SentFromMyHTC_Tattoo=NB165
[Click Android Development] Hanisa:
Try to restore an older nandroid backup that working for sure, maybe now you have something corrupt and if you do a nandroid you probably have problem in restore.
[Click Android Development] potattoo:
i tried to restore the oldest backup i made with clockwork 4.0.0.2, same md5 error :mad:

so either the checksum was written incorrectly or it cant be read correctly

can i fix the md5 manually? or should i try to downgrade to previous recovery and try to restore much older backups?

EDIT: to get my phone working ASAP, i flashed clockwork mod 3.0.2.7 and now could restore a backup from June...
[Click Android Development] marcelin99:
I tried N163 too. Everything working fine, but battery life is half day without any activity!!! Totally unacceptable for my wife!!!

I tried also CM-7.0 and nFinityGB with the same Battery drain issue.

I am coming from HTC Sence 1.6 (rooted version).

I did install AOSP 2.2.2 and Battery life is back to 3 to 4 days as with 1.6.

Note: All ROM tested at home, where I have poor network connection.
[Click Android Development] Vieira:
I installed nb161 (after full wipe) and the battery lasted for about 3 and half days. But today, after recharging, it quickly dropped (in an hour) to about 15-20% and I didn't even use the phone.
[Click Android Development] arco68:
Weird. Did you try a reboot and checked if the percentage was the same? Checked if any processes are using 100% of the cpu? Post a kernel log/logcat when this happens, if you can.
[Click Android Development] lupp0l0:
So, I'm not alone...
[Click Android Development] HeDone4eH:
:confused::eek: WTF

Since I went on Nb161 and then Nb 162 I got this problem

Put the phone charger in the evening and the morning encountered this problem with battery
[Click Android Development] noescape69:
I don't know if I must trust the battery indcator....

Yesterday afternoon, my phone is at 2%. I cut theradio. This morning, always at 2%. I take my phone, I turn radio and internet on, I download an application, I play for some minutes and read some news, and the phone is at 1%...

If I remember, in the past, at 2%, if I didn't have my charger with me, the phone turn off quickly...

So, is the battery indicator good ?
[Click Android Development] milos11136:
I have exact problem that you have described...In the morning my battery shows 100%, but when i turn on wifi or start doing everything else in less then a few minutes my battery droppes for 20-25%. I changed in cyanogenmod setting cpu governor from SMARTASS to ONDEMAND and now battery works normal.
[Click Android Development] KalimochoAz:
Really you made a clean install?

Do not recover backup. On my device battle works for 3 days without problems
[Click Android Development] andynroid:
ONDEMAND has been set.....Now let me see the outcome :)

SentFromMyHTC_Tattoo=NB165
[Click Android Development] Vieira:
Can you see if the battery start discharging as soon as it is charged, ie, if I leave it charging during the night and for instance it is charged at 3AM it then starts discharging even with the phone connected to power?
[Click Android Development] Hanisa:
With NB 167 we have for default microSD as primary storage or remain internal storage for default and we can choose after boot what to do?

Need a clean install?
[Click Android Development] andynroid:
Running too fast on ONDEMAND back to default

SentFromMyHTC_Tattoo=NB165
[Click Android Development] lupp0l0:
For me it's like you described.

During the first hours of the night the battery level is higher
[Click Android Development] unz:
I'm on nb162. For me battery is not draining too fast.

It's only misbehaving the charging process.

I charged the phone, after an hour it completed [100% icon].

Removed usb cable, battery % was 70 after using it for a while.

Re-attached the cable till 100% again and finally it was fully charged.

I thought the problem involved the battery stats, but wiping them out [after 100% charge] didn't solve.

G.
[Click Android Development] Hanisa:
With NB 160 i have no battery issue. So i don't think that is a kernel reading problem like some users talkin about in precedent posts.
[Click Android Development] marcelin99:
Yes, I did a full wipe (factory reset), no data backup and all applications reinstalled from market.

I tried different setup of CPU, incl. Powersave, without any noticeable difference.

I disabled 3G to keep only GSM: no effect.

I reduced also the display brightness: no effect.

In fact I got same battery drain issue with my Hero ( down from one and an half day to 6-8 hour) since CM sources moved to Android 2.3.5 in spite of full wipe, incl. ext-partition, factory reset, etc...

http://xdaforums.com/showthread.php?t=932377&page=424

Whatever the reason, thanks KalimochoAz for your great work.
[Click Android Development] marcelin99:
After a full night of charge, I noticed that indicator stayed at 100% for the first 4 or 5 hours, but suddently the chrge level is going down at high rate until the phone shut down automaticaly.

I tried to reboot immediatly after first ROM install as the required practice applied for the Hero. Then full recharge and wipe of battery stat. No difference.
[Click Android Development] lupp0l0:
Charging the phone while keeping it off lead to a full battery charge.
[Click Android Development] mitsakhs:
finaly a nb witha BIG CHANGELOG :D
[Click Android Development] andynroid:
Agreed n 78.11 Mb in size.....:D
[Click Android Development] nonoheran:
For me , allways ADW launcher very laguy to goes out sleep mode .... and sometimes FTC ......

is there a way to calibrate the level sensor ?????? my tattoo always gone on landskape mode !!

annyway , Very a good work
[Click Android Development] HeDone4eH:
And to me it happens:confused:
[Click Android Development] psyhound:
I've tried to reinstall the rom but it's even worse... opera mini force closed and completely crashed the phone. XDA app forceclosing, too!
[Click Android Development] xethjeh:
Use search in this thread.. U must instal older rom where ur GPS will work, turn up GPS and stay ON, reboot recovery and than flash back this rom. Point is in turned GPS ON on rom where working before.
[Click Android Development] xethjeh:
Never mind, for me ADW is lazy and laggy on every rom... prefering launcherpro or ADW EX
[Click Android Development] nonoheran:
OUUAA !!! Thanks a lot !!!!! my tattoo is another one !!! trying launcherpro !!

tattoo goes out sleep mode at light speed !!!!! and all on it too !! thanks !
[Click Android Development] emb0re:
Hey Kalim!

Awesome ROM :) Great work!

Maybe you should add the Market Patch D/L link to the first post of this thread (as you did on htc mania) :-)
[Click Android Development] KalimochoAz:
Asking for help

I don feel very confident to that Patch. As soon as people say that this patch works 100% I will post, but in Froyo I add Market patch and I spend a lot of time messaging and testing on it. My problem is the time, I want to make camera work 100% and maybe FM, and I cannot be with all users at the same time, but I like to be there helping. Sorry.

I know that most of you complian about why I post in HTCMania and then here... but for me is easy in Spanish, is not that I'm misprizin xda users. For sure you can help me a lot too.

I make a proposal for you, try to help me to make a better first post, so people can have all the info there.
[Click Android Development] KalimochoAz:
Start again from 0. Clean all. Copy your SD on PC and dormat SD.

Format system

Format data

Format cache

Install again and don't touch performance setting at cyanogen. ( at least at the begining )

Do not recover backups with a backup tool. I don't ensure what does tools do, and I cannot ensure it will work after backup.

Then all shoud work properly.
[Click Android Development] em0hawk:
I can't install 11.03. I have wiped and choose to install then get the following error:

installing update

assert failed: getprop("ro.product.device") == "click" || getprop("ro.build.product") == "click" || getprop("ro.product.board") == "click"

E:Error in /sdcard/KalinGinger.11.3.zip

(Status 7)

Installation aborted

Any ideas? I thought the zip might be corrupt at first so downloaded it again but no difference.
[Click Android Development] dancer_69:
Yes, to read the first post more carefully and to download and install the NEW clockworkmod recovery image
[Click Android Development] em0hawk:
Already have, 3.0.0.5 right!
[Click Android Development] androjm:
I installed ClockWorkMod 3.0.0.5 and I have the same problem !!!

assert failed : getprop("ro.product.device") == "click" || getprop("ro.build..product" == "click" || getprop("ro.product.board") = "click"

E:Error in /sdcard/KalimGB.11.3.zip

(Status 7)
[Click Android Development] petreski:
I have the same problem with 3.0.0.5 recovery !
[Click Android Development] em0hawk:
10.12 installs fine. it's just the latest 11.x version that won't install.
[Click Android Development] HeDone4eH:
Here NEWClockworkMod v3.0.0.5

That version only made to work for 11.02 and 11.03:cool:

Save it in memory card
[Click Android Development] androjm:
it is not the same 3.0.0.5 than this 3.0.0.5 ?
[Click Android Development] dvfk:
No it's different from the version in your link (thread 854152). I can't update to CM7 RC0 so I'll try this new version now.

IMPORTANT - remember to UNZIP first :) - first I wrongly I typed

su (... and the allow button)

cd sdcard

flash_image recovery clockworkmod3005.zip

but I should have unzipped and the last line should have been

flash_image recovery recovery.img

Now it works.
[Click Android Development] KalimochoAz:
There are more versions here of 3.0.0.5. Install te one at the first post, is the valid an oficial one