yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] PhoneMasta:
Baking installs the app but doesnt cause it to run when you hit the phone button on the bottom of the screen. So I tried a little experimentation..

and holy crap it worked (kinda sorta). I pulled Contacts.apk from /system/app and pushed it back as /system/app/HtcDialer.apk and now when I hit the phone button it pulls up the N1 app! only problem is it launches it in call log ... any idea on how to change the params so the phone dialer is displayed instead?

More info: launching contacts app by itself from the app menu shows this in the logcat:

I/ContactsListActivity( 213): Called with action: com.android.contacts.action.LIST_DEFAULT

I am guessing I need to modify some file somewhere to define the action to take when the "Phone" button is hit. This way I can launch the app with a different action...

Can someone with a stock N1 rom fire up adb logcat and launch the phone app to see what action is being specified to go to the phone dialer view?

I need another Nexus One it seems to tinker around :)
[Nexus One Android Development] xenosyde:
Yes, I wiped all
[Nexus One Android Development] pjcforpres:
Sorry, I got busy at work, then had to get dinner and what not.

Anyways, are you running a modded kernel? ie, one of the over clocked under volted, et al?
[Nexus One Android Development] xenosyde:
No. I'm able to get alpha7 installed perfectly fine, but any version above that doesn't work.
[Nexus One Android Development] pjcforpres:
Hmmmmm.... trying to think of every aspect that effects boot.img

Try this, open up the a10 zip and copy the boot.img to the tools folder of the SDK. Then try fastboot flashing just the boot.img

In case you don't know off the top of your head, boot into fastboot(hold down trackball while powering on), then open a command prompt inside the tools folder of the sdk by holding down shift, then pressing right click with the cursor located in a blank region of the folder.

Once again, make sure you have copied the boot.img from this ROM into the tools folder as well.

Then type:

fastboot devices (This makes sure you have fastboot access, should give something like HTC920402480249)

then type:

fastboot flash boot boot.img

If it fails, it fails, if it goes, then go back into recovery and try flashing this ROM again.
[Nexus One Android Development] pjcforpres:
Note:

If it flashes via fastboot, but not via recovery, you will want to just flash a working ROM and hopefully something or somebody will make sense of this.
[Nexus One Android Development] PISSANDVINEGAR:
Even after flashing A10 succesfuly my backlights for my capacative buttons do NOT work, and the trackball LED .so thing that I pushed works, but the colours won't change
[Nexus One Android Development] PhoneMasta:
Okay guys, I tried pushing N1 Email app to replace the Mail.apk in the desire rom and I was SOL. odex issues and then things didnt work so well. Contacts.apk can overwrite HtcDialer.apk and I havent seen any problems there. If anyone has other ideas or know better ways, I am all ears. I am really starting to like goofing around with this :)
[Nexus One Android Development] chmilu:
I have the same problem and I don't know how to solve it now.

I flashed via SD card, but radio remained unupdated.
[Nexus One Android Development] PhoneMasta:
Have you guys tried including the latest radio image (32.26.00.24U_4.04.00.03_2) via the kitchen on modaco's site? that flashes the rom, the flashes the radio image as well all in one go.
[Nexus One Android Development] chmilu:
not yet, that affects the signal as well?
[Nexus One Android Development] jp2000:
Couple of things I noticed:

1. When the phone is charging, the top LED does not light up at all

2. The UV kernel is sending a bit more voltage to the proc in idle mode, has this been changed?
[Nexus One Android Development] matthewboii:
Is anyone else experiencing the whole text messages from the future thing mine are out of order because it says they are received at random times that are a couple minutes after what time it really is
[Nexus One Android Development] jlevy73:
Yes radio = signal.
[Nexus One Android Development] s0lidjacks0n:
Google reader to news app?

anyone know how to add a google reader feed to the news app?
[Nexus One Android Development] jlevy73:
Paul was nice enough to post all the different radio versions. You can get them here: http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
[Nexus One Android Development] jlevy73:
Not that I am aware of. Have you checked our Readerscope from the marketplace. That is a good google feed app
[Nexus One Android Development] s0lidjacks0n:
I normally use newsrob, however I was just hoping to add it to the news app because of its awesome widget
[Nexus One Android Development] mudrock1000:
Great rom I actually do switch this and cyns from time to time.

Do you think you can get the camera app up soon? Thats really the only thing preventing me from using this rom as my main. The rest of the bugs are irrelevent to me (I still am unable to spell that)

Just a question. Is the camera problem in the rom itself or is it possible to port the n1 camera app itself to the rom as a temporary fix to have it run at full 5Mp and 720p? This is one of my most used features and it'd sure come in handy at times.

Anyways great work otherwise keep up the good work!
[Nexus One Android Development] chmilu:
Thanks,

jlevy73

I flased the new radio and hope it will go well.
[Nexus One Android Development] richardrahl:
trouble flashing Alpha 10

when I try to flash Alpha 10 rom I get the following error

"E:can't chown/mod /data/xbin/set_resolvconf (nosuch file or directory)"

"E:Faliure at line 370: set_perm 0 0 0755 Data:xbin/set_resolvconf"

I'm seeing that other people are using this rom, so could this be a problem on my side? has anyone else gotten an error like this?

thank you
[Nexus One Android Development] PhoneMasta:
Re 1. known problem. after flashing to the latest image, and rebooting a few times it seems to have gone away. But there are some quirks. This is an alpha build after all :)
[Nexus One Android Development] PhoneMasta:
HTC one has known issues and has been replaced by the stock N1 sms app in the current rom. Try out A10 and let us know if you experience the same problem.
[Nexus One Android Development] PhoneMasta:
Haven't seen that error. Try wiping data/cache before flashing. Are you using the latest greatest recovery rom which can be found here

http://xdaforums.com/showthread.php?t=611829
[Nexus One Android Development] :
I can get IMAP working. I was just hoping that someone can mod the email app to allow multiple exchange accounts.
[Nexus One Android Development] PhoneMasta:
I tried to get the Email app from N1 pushed into the desire rom to replace the current Mail.apk, but got tons of exceptions for .odex. Had to revert back for now. Hoping Paul or other senior folks can help out with some hints :)
[Nexus One Android Development] jlevy73:
Lol, I tried the same thing and gave up. Perhaps GodDriven can give this a go tomorrow.
[Nexus One Android Development] d.cortez:
you can use the Email.apk from one of Cyan's 5.0.x releases and push it to your device. i renamed it to Email2.apk, pushed to my device and was able to add my gmail account as an exchange account. i could sync my mail and contacts but that was it. since i didn't need a second exchange account i removed it.

EDIT: Also wanted to mention i pushed the CorCAL.apk to gain access to my calendar data; i did not test if you could combine this info with the Sense calendar widgets. i suspect it may be possible by going to the Sense calendar, Menu->More->Calendars and selecting my gmail account from the list of available calendars.
[Nexus One Android Development] lankri:
I remark that with this alpha version the Droid Wall do not work at all :(

Did someone have a solution.

Thanks
[Nexus One Android Development] a1t:
OC the kernal

Few questions. I am greatful to anyone who can help answers these.

-I am wondering if all I have to do to OC on all of these alpha builds is flash the OCkernal and replace the .ko in the appropriate dir. Is this correct?

-Camera flash. Another ROM claims to have this fixed however, when I flashed, it didnt work. What is the status on the fix for this ROM? Probably not prior to leaked version?

-Aps2SD. Any progress on getting A2SD on this ROM?

Thanks all for the help.
[Nexus One Android Development] saquib:
Nexus desire rom (alpha 10) - battery charging issue

Having some odd problems with battery charging using the desire rom's (currently alpha 10, but had issues on the other roms):

1 - charging battery via mains or usb, and charging light appears but battery icon does not indicate charging is taking place, and battery carries on draining

2 - battery gets stuck on 100% for a long time (e.g. 15 minutes) even when phone is being used intensively

etc.

Tries to drain down to 0% and re-charge, which seemed to help for a while. First time the battery got to about 15% and then went striaght to 0% and next time when to 0%, so appears to be some sort of calibration issue ? I did clear the battery stats via the option in the custom recovery image, not sure if that has created some of these issues ?

Please help!

P.S. Cross-posted to modaco.com as well.
[Nexus One Android Development] grainysand:
Mine's charging fine to me, running the same ROM as you. What kernel have you got on?
[Nexus One Android Development] grainysand:
It's available in the online kitchen. But if you don't want to pay for the subscription, you can do it the "hard" way and take a look at this thread. Note: I did it for alpha9, it worked, but it caused my attempt to flash alpha10 to fail miserably. I ended up having to wipe my prior ext2 partition. Presumably, Paul's apps2sd script is tailored to work with his ROM with less, uh... breaking.
[Nexus One Android Development] saquib:
Not sure :-( Just applied to alpha10 and that's it. Should I apply something else afterwards ?

Thanks for your reply.
[Nexus One Android Development] grainysand:
I think it's the kernel included since alpha9 which, while not causing me any trouble personally, seems to have played funny buggers with several peoples' battery/charging. You could try flashishing this kernel. Or else you could try flashing a boot.img from an earlier alpha, say 7.
[Nexus One Android Development] paulobrien:
Hi Guys (and gals)!

Thought i'd drop in and catch up / update one last time prior to heading offline until Tuesday!

I'm sure you'll all be active in this topic while i'm away, what I love about communities is how everyone helps each other out etc., when I'm back i'll catch up with all the latest developments / requests / fixes etc., who knows, maybe we'll have a new drop from HTC by then (fingers crossed!) :) Ad Free / Plus members, if there's anything you'd like to see in the kitchen that isn't there yet, do share and i'll do my best. One REALLY exciting thing I plan to add next week is a little button that lets you upload your own zip file (up to 10MB) which then gets merged into the ROM update zip. So if you'd like something if your own baked into /data or /system, you can do that! :)

With regards to the outstanding problems with the build, it is kinda tricky because at this time we don't know what works on a real Desire and what doesn't, i.e. what is a problem with the ROM and the what is a problem with the port. I notice that a few other devs are basing on my ROM now, which is cool, it means they too are working on fixes and will hopefully contribute them back!

The 3 main 'issues' as I see them and their current status...

- Bluetooth - Bluetooth is patchy / unreliable and although i've spent a lot of time on this, there's no real progress yet. The Bluetooth libraries in the Desire ROM are pretty different to the N1 ROM (in a good way - they have more services I believe), but this does mean it's non trivial to 'switch in' the N1 ROM libraries at this time.

- Camera - I see manup has got the flash working in his ROM now, which is cool - he's a good guy so i'm sure he will contribute this back to the wider effort. Given time and persistence, the Camera app can also be modified to enable 5 Megapixel mode. I'll look into this on my return if it's still an issue and we haven't had a new Beta drop.

- Missing Market Apps - this is the real weird one - I can't really see why this is happening. In the past, Market contents have been based purely on the device's fingerprint (which I have deliberately set to match the N1 ERD79 intial release for compatability) and the operator identification. I've dug into this one pretty deeply, the one thingI suspect and haven't pursued yet is that the device's properties from the RIL are somehow being incorrectly reported by the OS, although if that was the case, Market Enabler should fix it. If anyone wants to pursue this, I would try the following...

- download and install Market Enabler from here (don't run it yet)

- type 'adb shell rm -f /data/data/com.android.vending/cache/* && adb shell killall com.android.vending'

- run market enabler and set the region to T-Mo/USA

- test the market!

And with that, i'm outta here, the snowboard is waxed and the powder beckons... :D

P
[Nexus One Android Development] Huey85:
Have an awesome trip P! Hope you all R&R'ed by the time you get back for some more desire-able cookin' ;)
[Nexus One Android Development] mgorman:
I tried what you said about the market enabler and that didn't work
[Nexus One Android Development] paulobrien:
Oops, missed out the line '- run market enabler and set the region to T-Mo/USA' in the instructions, fixed. ;)

P
[Nexus One Android Development] mgorman:
still didn;t work
[Nexus One Android Development] GodDriven:
Thank You...

Thanks for all that you've done.. it has been a very tricky ride up to where you have brought us. I wanted to say I hope you have fun.. It's 1 over there as I wake up to 8am over here and a pile of snow.. wish you were here, Jersey just got a Nor' Eastern.. we have snow falling the size of rocks now... it on my avatar, and since to you people can see what Sense UI looks like when it pours the white powder..

Have fun there skipper, I believe all your work has always been enticing.. always.. but, this has been the ultimate job you've ever pulled off... Funny how you'll be..on vacation, but, can never forget your passion... Have Fun... Lol...
[Nexus One Android Development] tizzl10:
...and be safe. we need you back in one piece.
[Nexus One Android Development] hkfriends:
anyone know how to make the camera flash to work?

thx
[Nexus One Android Development] GodDriven:
Edit: I just tried the Market Enabler Item and sad to say.. I believe this doesn;t fix it either paul.. I tried twice.. No Result..

new-host:~ GodDriven$ ./adb remount

remount succeeded

new-host:~ GodDriven$ ./adb shell rm -f /data/data/com.android.vending/cache/

rm: /data/data/com.android.vending/cache: is a directory

new-host:~ GodDriven$ ./adb shell killall com.android.vending

new-host:~ GodDriven$

Everything Went well as you can see... Just didn't go well on the device.. Thought I'd give some input on that.. :mad: :(
[Nexus One Android Development] fantimur:
Hello,

Could somebody help me to use HTC Sync with this ROM?

My configuration:

- Windows 7

- HTC Sync 2.0.18

- USB debogging checked on the phone

- Nexus driver ok in device manager

- HTC Sync selected on the phone under PC Connection

When I plug my Nexus, nothing happens with HTC sync. It stays gray...

Thank's a lot for your help.
[Nexus One Android Development] xenosyde:
Problems flashing above alpha7

I assume I am performing all of the correct procedures (nandroid backup, wipe data + dalvik, flash rom from zip). But I am unable to perform any rom flash past alpha7. The only rom that works is alpha7. I continuously get this error flashing any newer version:

E: Error finishing BOOT:
E: Failure at line 378:
write_raw_image PACKAGE:boot.img BOOT:

It does not complete flashing, it aborts after the error.

Stats:

Baseband: 32.24.00.22U_4.03.00.21_2

Kernel: 2.6.29.6-cm-teknologist-0.2

What I've tried:

I've tried going from stock to any version above alpha7.

I've updated my recovery from 1.6.0 to 1.6.2.

I've matched the MD5sums on the downloads.

I've cleared the storage in fastboot.

I've tried flashing the alpha10 boot.img from fastboot, but fails.

The error still persists. Any help is appreciated, I would love to use newer versions.

Thanks in advanced for any possible solutions...
[Nexus One Android Development] jdoo:
Wow that sucks man! Have you seen this thread?

http://xdaforums.com/showthread.php?t=637882
[Nexus One Android Development] GodDriven:
Wipe...

Okay, I believe that at alpha 7 you had to do a full wipe... now, wipe the dalvick cache.. factory reset and wipe.. great app to have in handy is reboot control widget.. trust me you'll love it..

After the wipe has been done, download the 1.7 from modaco and flash that.. this will sort of bring you out of the sense UI ordeal on the device.. once you've signed in did all your stuff... now hit back to recovery, wipe everything again, sorry, for the long list, but it all. Depends on internal memory such as cache, data that needs to Cleared.

From here flash your sense UI and everything should work, sometimes things stay written... anything?
[Nexus One Android Development] ivanxx:
Exchange not Syncing / No H/3G/E/nada

Hi there!

I'm on A10 now and I'm having a problem with the Exchange Syncing (it begun when I hop on A7, I think). It just won't sync while the phone is sleeping. I've got it configured to sync each 15 min. but that only works if the screen is on.

Also, maybe this is related with the other problem: I loose data connectivity over the GSM interface and have to force a network mode change ('Only GSM' to 'Auto GSM/WCDMA' or vice versa will do). This way the whole GSM radio seems to go off and on again, and then data is back... I cooked and installed a ROM with the latest radio update already, but no joy...

Any bell ringing? Thanks! :)
[Nexus One Android Development] xenosyde:
In my recovery.log I noticed this is happening when wiping:

Wiping data...
Formatting DATA:...
mtd: not erasing bad block at 0x00400000
mtd: not erasing bad block at 0x044a0000
mtd: not erasing bad block at 0x05240000
mtd: not erasing bad block at 0x05300000
mtd: not erasing bad block at 0x06260000
mtd: not erasing bad block at 0x0bee0000
Formatting CACHE:...
mtd: not erasing bad block at 0x03160000

Data wipe complete.
[Nexus One Android Development] GodDriven:
As i Said...

Okay as I stated before you have somethings still written.. okay, so was this before applying the other Rom or just as a wipe.. okay, we have to bring your phone back a bit.. go to your oldest nandroid back up and restore that one.. this should re lay out your partitioning and clear those bad blocks.. I hope your okay with this after the nandroid, remember those are God in this business. After you resotre, perform a wipe again which should clear up the issue...

Also if anyone can help this nice individual with further knowledge in what it means to have errors as your wiping the device stating it cannot be erased due to it being a bad block... thanks in advance..
[Nexus One Android Development] PhoneMasta:
@GodDriven, nandroid backup, are you referring to titanium backup? :confused:
[Nexus One Android Development] GodDriven:
No sir.. you know that back up you make in the now lovable career recovery... okay, restore that.. a titanium back up only covers apps and a few settings. Nandroid is the picture taken of your device. Sydtem, boot, data, meta files.. get it...

Go into recovery, nice app is reboot control widget and when up, tap recovery console.. three select nand restore..
[Nexus One Android Development] lordshido:
is there any way to display 3g instead of H with this rom?
[Nexus One Android Development] lightforce:
Can anyone get to the market?
[Nexus One Android Development] mgorman:
Ya. No market problems here. Only problem I have is voice input. Did you wipe before you flashed?
[Nexus One Android Development] 7wonders:
yep, with and without marketenabler activated
[Nexus One Android Development] lightforce:
yea i wiped.

i get the android terms and it just closes out the market
[Nexus One Android Development] GodDriven:
Little Fixes...

Paul, Google voice is stll doing the the message and call statement i noted earlier. The mount is not working, no biggie just do it through recovery... Oh If not noted the Live Wallpapers Tab brings up the regular wallpapers, photos bring up the live, wallpapers tab bring up the photos... No biggie either..

Other Than that, I SEE no other issues with this release. Great job there, I mean you must amaze yourself how fast you react to things...
[Nexus One Android Development] darkstar38:
Awesome ROM Modaco! I can tell this is going to be sweet when everything is working properly.

Only a couple bugs:

1. Sync is stuck on its been over an hour, tried both wifi and 3g. After a reboot it seems okay

2. Downloaded N1 Torch and there is a big pixel "Block" on the strobe button. Also when exiting the app after the led has been on then off and pressing home button the " turned led off" stays on sometimes for a while.

3. Messages FC at boot up.
[Nexus One Android Development] mgorman:
Can anyone confirm that voice to text and voice search aren't working
[Nexus One Android Development] lightforce:
I can confirm my Voice to text isnt working.

also BT
[Nexus One Android Development] GodDriven:
Right There With You..

I am seeing that the voice input dosn't work either.. I flashed the ime keyboard zip thats on the forum and IT NOW HEARS ME, it just states that there a problem with the network connection??? Moving on, I moved on to Better KeyBoard 4.5 and it picked it up and typed it.. It may not show in the message box but it will show it in the line where it makes corrections i.e. when your initially typing before you press enter...

I mean that is not a full fix, don't recommend flashing the keyboard to anyone either, i guess it suffers from redundency... But.. use another keyboard that accepts voice and you should see something...

LMK...:o
[Nexus One Android Development] marra2:
Can someone in uk test to see if tvcatchup.com works as it requires flash !

thanks in advance :)
[Nexus One Android Development] bmore1380:
ive been using the rom for sometime runs really good it looks nice for day to day usage i hardly use camera and things like dat really nice job modaco u do great work dont let no one tell u any diffrent
[Nexus One Android Development] m00moo:
small bug noticed.

when changing wallpaper, the categories seem to be messed up.

eg. Live wallpapers would take you to gallery etc.
[Nexus One Android Development] dtobin:
Not working for me. :(
[Nexus One Android Development] GodDriven:
STATED.. It...

Thanks MooMoo for the reminder.. I stated it when I let him know that Google Voice Dosn't call out with the assigned google number instead uses the carrier assigned number.. Text's work fine...

Check that out ppl... :eek:
[Nexus One Android Development] marra2:
thanks dude !
[Nexus One Android Development] kingklick:
we still need to fix the white screen after reboot........

damn its annoying!
[Nexus One Android Development] lightforce:
No wite screen here
[Nexus One Android Development] seraphimserapis:
haven't any problems with that, too!

but: my google calendar doesn't sync
[Nexus One Android Development] minelbp:
white screen was fixed a while ago on modaco's build. One of the reasons I have yet to try yours out, king. Looking forward to it since yours tend to be quite snappy in certain situations.
[Nexus One Android Development] GodDriven:
On Your Own...

Dude, I have not seen that... Once... So your on your own if your cut of this Rom is having it or your just having it yourself. Lmk...

What I can advise to you is what Paul said, do a full wipe and move on...
[Nexus One Android Development] PhoneMasta:
Ah..sweet. Useful to have :) thanks man.
[Nexus One Android Development] mgorman:
Ya. Go into the framework-res.apk and resources.apk and make a copy of the 3g icon and replace it with the h one and then push them to the phone
[Nexus One Android Development] PhoneMasta:
...removed....