Database Info

is it worth getting google N1?

Been looking around alot for my first ANDROID device and thinking about getting the N1 but it seems the device has lotta issues.muti-touch problems,sms mms automatic deletion etc.....what do u guys think should i get it or not.if i flash the DESIRE rom will it fix all the issues the NEXUS has?thanks

I really like mine but if you are on the fence I would suggest waiting for something better. The OLED screen, while offering great contrast in doors, has serious visibility issues out doors. Also the cheap touch sensor really does suck. I have to use difficult controller layouts in game emulators because the phone has trouble recognizing dual touches on the same axis.
If it wasnt for those two issues i would totally tell you to jump on board. But i think you should wait for something similar with a better touch sensor and an LCD or Super AMOLED.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

yea it would be pain to play multi-touch games if the multi-touch actually doesnt work well.i did checked few videos of the nexus one reviews and cons,overall its a good phone but maybe i shouldn't give google the $530 unless they fix all the bugs.but what if i FLASH the DESIRE rom will it improve anything on the N1?

There is also the hardware problem with the 3G radio design(search youtube: Nexus 3G Problem)

GHOST99K said:
Been looking around alot for my first ANDROID device and thinking about getting the N1 but it seems the device has lotta issues.muti-touch problems,sms mms automatic deletion etc.....what do u guys think should i get it or not.if i flash the DESIRE rom will it fix all the issues the NEXUS has?thanks
Click to expand...
Click to collapse
Yeah it has some minor issues, but the only one that actually bothers me is the crazy screen problem (which they promised to fix in 2.2), where you gotta turn the screen off and on to fix it. Which isn't a huge deal anyway.
If you're on verizon, and don't mind the design of Incredible, get that one. If not, then I say pick N1/Desire, they are pretty much the same (I prefer N1 because of the design and noise-cancelling mics).
Otherwise, doesn't matter which device you get, as long as it's android... this OS is freaking amazing, I swear.

lineman78 said:
There is also the hardware problem with the 3G radio design(search youtube: Nexus 3G Problem)
Click to expand...
Click to collapse
There is no 3G problem with new N1s, it's been confirmed many times over.

love my N1 but the incred may be worth getting.. only 2 days away. I just don't like sense but since you are thinking of doing the desire rom then you must want sense and the incred is better than the desire in a few small ways.
also if you have time don't rule out the 4g evo... on sprint and verizon summer so the rumors have it.
I went with N1 because you get the android OS updates months before anyone else because it's 100% stock.

thanks to all of u but UNFORTUNATELY im with US t-mobile so i have done all my research of upcoming gsm ANDROID for this year but nothing stands out but the nexus one.i have checked if the INCREDIBLE or the EVO was WORLDPHONE(cdma service with GSM sim slot like the touch pro 2 in sprint)but officially they not.its really sad for us gsm carrier users.so i guess i might take a chance at N1 because its better than the current phone im using(hd2).

@GHOST99K
I think it would be better to wait for Google I/O. That's just 3 weeks from now and many things could change then

thanx im gonna wait another month and c whats up with google.

i really want the N1 but i love a good qwerty. wish Tmobile would get the Milestone isnt Motorola suppose to be working on the "N2 with a qwerty?" this would make me very happy.
Sent from my HTC Dream G1 using the XDA mobile application powered by Tapatalk

i love my N1, but i wouldn't rule out the incredible, if you are looking at phones. and, if you can hold out, the evo should be a rockstar.
the incredible does have a few hardware one-ups on the N1. i have never had a problem with my screen only being dual touch, because i don't game on it. the camera is supposedly better on the incredible too. otherwise, they're essentially the same phone. and, because i'm rooted with unlocked bootloader, i am able to put the desire's (basically the same as incredible) ROM on it. i don't care for sense though. i don't know that the unlock methods for the N1 will work on the incredible, which may mean that you are stuck with sense on that phone, like it or not.

which may mean that you are stuck with sense on that phone, like it or not.
Click to expand...
Click to collapse
You can easily switch to the default android home on a stock sense ROM. All you have to do is go to sense in applications and clear defaults.

you guys make me think I should return my N1 .....
??
damn I try not to think how much I spent on it though, ridiculous...but at least it is not on a contract

lineman78 said:
You can easily switch to the default android home on a stock sense ROM. All you have to do is go to sense in applications and clear defaults.
Click to expand...
Click to collapse
Not on 2.1 sense thats stock. Thats only on flashed roms. I couldnt do it on my Incredible sooo...

That's interesting. I was able to do it with my hero. I am also able to do it with the fresh ROM, but Launcher2 could have been added and not included in the leaked Sprint ROM. I believe it was mentioned that the vanilla lock screen was in the leaked ROM, but broken. Since I do not plan on reverting to the sprint ROM, I will have to rely on some very patient person to let us know if this is true for the Hero too. Although Launcher2 runs so slow I could only imagine using it on an overclocked Hero.

Changing the bluetooth stack in Android?

How easy/difficult is it to achieve this feat, and is it a kernel dependency? Main reason I ask is that Sense UI is almost perfect, but it's BT stack is the only flaw, and for some a glaring one. How would one going about replacing HTC's deficient version with, say, Koush's Cyanogen Mod version which seems to work flawlessly? Thanks in advance for any answers or insight!

Azuran said:
How easy/difficult is it to achieve this feat, and is it a kernel dependency? Main reason I ask is that Sense UI is almost perfect, but it's BT stack is the only flaw, and for some a glaring one. How would one going about replacing HTC's deficient version with, say, Koush's Cyanogen Mod version which seems to work flawlessly? Thanks in advance for any answers or insight!
Click to expand...
Click to collapse
no one knows? i would have thought for sure somebody here would have done it or know if its possible. I'm looking for this as well

Bump... I've been asking the same question myself recently. I have an HTC Evo 4G and love my Sense-based ROM, but I hate the fact that I can't use certain Bluetooth accessories with it (ahem... Wiimote). Does someone have an answer?

Perfecteagle said:
Bump... I've been asking the same question myself recently. I have an HTC Evo 4G and love my Sense-based ROM, but I hate the fact that I can't use certain Bluetooth accessories with it (ahem... Wiimote). Does someone have an answer?
Click to expand...
Click to collapse
I'll love to do that too !!
did you find a solution yet?
thanks

giloser said:
I'll love to do that too !!
did you find a solution yet?
thanks
Click to expand...
Click to collapse
Simple answer is no. You can try a CM based rom that gives you those options but the stacks cant be swapped due to driver problems. It is a give an take. The Default has better strength and range but is missing a few unneeded option (PO), while CM uses Bluz stack which gives you the option but you lose some BT signal strength and range.

Rogers G1 2.1 Update for the T-Mobile G1?

Can the 2.1 version for Rogers can put onto the T-Mobile version of the HTC Magic or will it be problematic?

Looks like it works on 32a
http://twitter.com/Amon_RA/status/24101277025
http://twitter.com/Amon_RA/status/24113346424
http://twitter.com/Amon_RA/status/24116479740

Yeah i'm curious if it can be ported to us on 32b. Would probably work smoother than those legend ports
Sent from my U20i using XDA App

Anyone know if this has "Smart Dialer"?
Sent from my HTC Dream SparksMod using XDA App

is it sense ui?

asb123 said:
is it sense ui?
Click to expand...
Click to collapse
Yes it is sense

http://www.youtube.com/watch?v=1lNeYGQWymM

Come On Dudes! Do It! A Magic Sense Rom must run good on the G1!

Maybe somebody could replace the Sense UI for the Android original. The hardware is not so different, just a little bit more memory.
I want this ROM ported to HTC Magic 32B because since Android 2.x we always have memory leaks in the camera driver.

I definitely want this ported!

I definitely want this ported too! Especially if it finally bring Sense to the G1 without draining our battery in less than day. Or in another cases requires so many changes that it becomes too unstable.

hmmm what did rogers do that cyanogen didn't?

qipengart said:
Can the 2.1 version for Rogers can put onto the T-Mobile version of the HTC Magic or will it be problematic?
Click to expand...
Click to collapse
Some1 ported to 32b please please please

R3N0V4D0 said:
hmmm what did rogers do that cyanogen didn't?
Click to expand...
Click to collapse
Dude its Sense I love sense = o )

solaresdonis said:
Dude its Sense I love sense = o )
Click to expand...
Click to collapse
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.

I definitely am up for a port
Sent from my Htcclay's SuperBad 3G using XDA App

jcarrz1 said:
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
Click to expand...
Click to collapse
Another thing to remember is that 32A's have about 100 mb more ram, so 32B's actually need some of those things to make them more usable. Anybody know anything about the radio that released with it? I mean, is it still a locked down 3.X rogers radio, or is it something 2.X, or even 6.X? Another thing of interest would be bluetooth, but I'm not sure if 32A's and B's share the same bluetooth chip. +1 for the port jcarzz, I would try it myself but I'm still learning. We should also try to extract the camara drivers, the way I understand it in CM5/6 we're using a hacky method with backported donut drivers and a few other things. We could really pull a lot from this.
Okay, so I looked a few things up and answered some of my own questions. It does include a new radio 6.35.16.19, but it's not something we can use. Maybe some of the guys who have JTAG equipment can experiment with flashing it. Since it's not a G1 radio we shouldn't get bluetooth working so cross that off the list too. Still a promising release though.

jcarrz1 said:
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
Click to expand...
Click to collapse
Please my liege. Do it.
Request: Make it awesome .

mejorguille said:
Another thing of interest would be bluetooth, but I'm not sure if 32A's and B's share the same bluetooth chip.
Click to expand...
Click to collapse
No, just like all the early 1.5 Hero roms that were from 32a phone... no Bluetooth.
I did a quick dirty port... got to boot but runs like crap... nonstop FC's and crashes. Really no time to play with it.

fishman0919 said:
No, just like all the early 1.5 Hero roms that were from 32a phone... no Bluetooth.
I did a quick dirty port... got to boot but runs like crap... nonstop FC's and crashes. Really no time to play with it.
Click to expand...
Click to collapse
Hehe I figured so, but I wasn't rooted yet when all the hero rom's started coming out so I didn't know that til now. And I looked through cyanogen's twitter and he mentioned that the camera drivers were tied to the radio so we can't pull that from it either. GL on porting it.

[Q] Android ICS on Galaxy 5 i5500?

Guys, I know this phone is far from being a good one like Galaxy S, for instance, so I'm kind of guessing the answer here will be no, but...
Will I be able to install ICS on this phone? Like get the source, compile and install over the Froyo I currently have? Can I already do it?
Or this phone won't be good enough to run it? Or maybe it won't work as well because of its functionality (e.g. I already have physical buttons for home, going back, etc; would I be able to toggle off the virtual buttons for these on the screen?)

http://www.madteam.co/forum/index.php
They may be starting it here soon

Peterson Silva said:
Guys, I know this phone is far from being a good one like Galaxy S, for instance, so I'm kind of guessing the answer here will be no, but...
Will I be able to install ICS on this phone? Like get the source, compile and install over the Froyo I currently have? Can I already do it?
Or this phone won't be good enough to run it? Or maybe it won't work as well because of its functionality (e.g. I already have physical buttons for home, going back, etc; would I be able to toggle off the virtual buttons for these on the screen?)
Click to expand...
Click to collapse
The phone is capable enough for running ICS. The port will begin shortly at madteam.co/forum

if it is stable enough it would be great. I have read that even gb is not perfectly stable..

Almost every phone can (my old htc hero have a port and its 2 years old) the thing is to have someone with your phone...even you that have the guts to try to make it possible and stable but official i doubt it jejeje
Sent from my €PΩ 4G TØU©H

BT on Sense 4.0 builds

Rather than annoy devs on each Sense 4.0 post I thought I'd ask this simple question here as the BT problem is the same on each build.
BT was never working until Mdeejay fixed it (from memory). However, all the builds seem to only have a partially working fix as I cannot get my car to fully connect anymore (fine on Sense 3.6 etc).
My question is...is it a known issue that its a partial fix or do Sense 4.0 BT just not work with all devices. I need my phone to connect to my car and am happy to wait but perhaps I'm waiting for something that'll never happen!
Thanks for any heads-up

jamesbond_28_007 said:
Rather than annoy devs on each Sense 4.0 post I thought I'd ask this simple question here as the BT problem is the same on each build.
BT was never working until Mdeejay fixed it (from memory). However, all the builds seem to only have a partially working fix as I cannot get my car to fully connect anymore (fine on Sense 3.6 etc).
My question is...is it a known issue that its a partial fix or do Sense 4.0 BT just not work with all devices. I need my phone to connect to my car and am happy to wait but perhaps I'm waiting for something that'll never happen!
Thanks for any heads-up
Click to expand...
Click to collapse
Hi,
BT stack is notoriously poor on the Sensation.
I have seen some people using the latest FAUX 005b1 KERNEL on their Sense 4.0 ROMS .
He has had a degree of success in improving the BT stack.
Might be worth a try.

malybru said:
Hi,
BT stack is notoriously poor on the Sensation.
I have seen some people using the latest FAUX 005b1 KERNEL on their Sense 4.0 ROMS .
He has had a degree of success in improving the BT stack.
Might be worth a try.
Click to expand...
Click to collapse
Thanks. Rather embarrassingly I have never swapped the kernel that's already included in the Rom so that might be a challenge. I'll read around and see if I can do it as I like the idea of this kernel having an improved BT stack.

jamesbond_28_007 said:
Thanks. Rather embarrassingly I have never swapped the kernel that's already included in the Rom so that might be a challenge. I'll read around and see if I can do it as I like the idea of this kernel having an improved BT stack.
Click to expand...
Click to collapse
Hi,
Not difficult at all.
MAKE A NANDROID BACKUP.
Wipe cache and dalvik,
Flash kernel like a ROM.
Et voila.

Just worked that out (minus the wiping bit so not sure what I've got now )

jamesbond_28_007 said:
Rather than annoy devs on each Sense 4.0 post I thought I'd ask this simple question here as the BT problem is the same on each build.
BT was never working until Mdeejay fixed it (from memory). However, all the builds seem to only have a partially working fix as I cannot get my car to fully connect anymore (fine on Sense 3.6 etc).
My question is...is it a known issue that its a partial fix or do Sense 4.0 BT just not work with all devices. I need my phone to connect to my car and am happy to wait but perhaps I'm waiting for something that'll never happen!
Thanks for any heads-up
Click to expand...
Click to collapse
Mdeejay only partially fixed Bluetooth - look @rootzwiki it says Bluetooth fix part 1 (media) in changelog
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

Jonny said:
Mdeejay only partially fixed Bluetooth - look @rootzwiki it says Bluetooth fix part 1 (media) in changelog
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Ahh, I see. The faux kernel made no difference and now I know why. Couldnt find that changelog but at least I know a part 2 is likely!

Has any of the dev's been able to slove the bluetooth issues as yet on sense 4. roms or near to solving the issues.

BT Fix?
Same here, like most Sense 4.0 Roms that I have tried out have been almost near perfection right up until you get to the bluetooth part, like it really bugs me cause i'm normally on my BT majority of the time. Does anyone have any idea of an ETA on the fix? Cause I really would like to go back to Sense 4.0 instead having to use Sense 3.6 still

Anthonyburton100 said:
Same here, like most Sense 4.0 Roms that I have tried out have been almost near perfection right up until you get to the bluetooth part, like it really bugs me cause i'm normally on my BT majority of the time. Does anyone have any idea of an ETA on the fix? Cause I really would like to go back to Sense 4.0 instead having to use Sense 3.6 still
Click to expand...
Click to collapse
One rule of CyanogenMod which probably applies here is don't ask for ETA it is done when its done
Sent from my Sensation using xda premium

Anthonyburton100 said:
Same here, like most Sense 4.0 Roms that I have tried out have been almost near perfection right up until you get to the bluetooth part, like it really bugs me cause i'm normally on my BT majority of the time. Does anyone have any idea of an ETA on the fix? Cause I really would like to go back to Sense 4.0 instead having to use Sense 3.6 still
Click to expand...
Click to collapse
Eta = when it's ready/fixed.
That goes for ANY project on xda/rootzwiki/etc.
It's not like these guys are getting paid to do this, nor is it their job title of "developer".
Sent from my Sensation using Tapatalk 2

Anybody know of a 3.6 rom that has working bluetooth voice dialing?

geoffcorey said:
Eta = when it's ready/fixed.
That goes for ANY project on xda/rootzwiki/etc.
It's not like these guys are getting paid to do this, nor is it their job title of "developer".
Sent from my Sensation using Tapatalk 2
Click to expand...
Click to collapse
I agree. And for clarification, I didnt ask
I know I could just check the change logs on the each Rom but is there anywhere I can go to see progress or updates on this issue? Something about rootwiki but no idea where to look!
Thanks.