Database Develop

[Q] What ROM do I have?

I bought a slightly used Nexus One, the guy said it's rooted, well I am new to Android, just trashed my iPhone.
Anyways my OS seems slow at times, I have Froyo on it FRF91, but I think that it's a rather instable custom ROM how do I know if it's the original Google ROM?
I rather have the original Google ROM also because I like my phone to be able to get OTA updates.
If this is a Custom ROM, how do I get the OEM ROM back on my Nexus One?
Thank you all

If you go to About Phone in the settings menu it will normally have an abnormal name in the Kernel Version. What does yours say?

Blueman101 said:
If you go to About Phone in the settings menu it will normally have an abnormal name in the Kernel Version. What does yours say?
Click to expand...
Click to collapse
Even better, download and install any one of many screenshot apps. Take a screenshot of your About screen, and post it here?!
DroCap2 is my fave.

Tried drocap2 it didn't safe the screenshots where it said it did my kernel is:
[email protected] #1

You have an old version of Enomther's TheOfficial ROM (which is an excellent ROM, I happen to use it).
Flash its latest version (thread in Development section), and if the launcher (desktop) speed is what's bothering you - install LauncherPro. This ROM is probably one of the most stable custom ROMs out there, if not the most stable of them.

Jack_R1 said:
You have an old version of Enomther's TheOfficial ROM (which is an excellent ROM, I happen to use it).
Flash its latest version (thread in Development section), and if the launcher (desktop) speed is what's bothering you - install LauncherPro. This ROM is probably one of the most stable custom ROMs out there, if not the most stable of them.
Click to expand...
Click to collapse
+1
I love Enomther's roms and would highly recommend you to upgrade to the newest version.

Glad to hear it's a good ROM it's not often but sometimes when closing an app it takes about 30 seconds till i can do anything else.
How do I upgrade to the newest ROM? I went to the webiste of Enomther and it says something about Radio update also I like the stock theme will that stay on my phone?

1) It's definitely not a ROM problem. When installing his new ROM, wipe EVERYTHING - data and cache, and install apps one by one until you find the offender.
2) Flash his non-themed version and you'll get a stock look.
3) Check your baseband version in the same place you've checked kernel. If it says *U_4.06* or *U_5.08* then you don't need to flash the radio, if not - go to Nexus Wiki / Radios and look there.

Thanks a lot I will try it today.

Just did the update also installed the HTC 720p camera update.
Now it says:
Baseband version: 5.08.00.04
Kernel Version: [email protected] #1
Build number: FRF91
is that the right thing?
Thank you so much for all the hints.

Yes, you have the latest. See if the newer radio works well for you, and if it doesn't - try flashing the 4.06 version.

Themed, ROM'd, deodexed 2.3.15 to OTA FroYo... is it worth it?

In order for me to go back, I'll have to sbf to 2.1u1 and lose many hours spent customizing my phone the way I want. I want it to be worth it, not just as a way to hide the fact that I voided the warranty.
Can someone list here an impromptu changelog of the diffs between 2.3.15 to 2.2 OTA? Thx.
Sent from my DROIDX using XDA App

A new possibly stronger locked bootloader is enough of a change for me not to update
Sent from my DROIDX using XDA App

gunkle said:
A new possibly stronger locked bootloader is enough of a change for me not to update
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
They just changed keys from the previous bootloader, not made it stronger from what I understand. It'll be a moot point once someone gets a 2.2 sbf. Still, I want to know what benefits, if any, there are between 2.3.15 (or just 2.2 leak) and the 2.2 OTA.

SirBrass said:
They just changed keys from the previous bootloader, not made it stronger from what I understand. It'll be a moot point once someone gets a 2.2 sbf. Still, I want to know what benefits, if any, there are between 2.3.15 (or just 2.2 leak) and the 2.2 OTA.
Click to expand...
Click to collapse
One benefit is to the OTA is the updated Kernal. As of now, we are still on the kernal from the first 2.2 leak.

What benefits does that bring?
EDIT: Tweet from the ever-astute P3Droid:
If you don't need the newest radio .07 or the newest kernel then I would not take the OTA, I refused it on my phone.
Click to expand...
Click to collapse
He lives in the same area (same county, same metro area) that I do, so if he doesn't need the newest radio then neither do I (unless the newest radio... and by that I assume he means the CDMA and phone radio(s), not the FM radio app, has better low-signal strength receive abilities). I'll hold off till birdman gives us that rooted OTA (and hopefully deodexed as well).
TBH also has promised something VERY nice on Friday (assuming this OTA hasn't knocked that something down into 2nd place priority for them).

A friend of mine who did the OTA said his kernel was still at 2.6.32.9 . the characters following that (which I think is just a build time stamp?) is different.
So I question whether its really a newer kernel, or just a newer compile/build of the same source?

Yeah I'm staying on 2.3.15 leak until at least we get 2.2 sbf. I don't really see a point of upgrading right now and putting myself at risk of having the phone bricked, since 2.1 sbf will be useless.

meshdub said:
Yeah I'm staying on 2.3.15 leak until at least we get 2.2 sbf. I don't really see a point of upgrading right now and putting myself at risk of having the phone bricked, since 2.1 sbf will be useless.
Click to expand...
Click to collapse
+1 main reason not to use the OTA

meshdub said:
Yeah I'm staying on 2.3.15 leak until at least we get 2.2 sbf. I don't really see a point of upgrading right now and putting myself at risk of having the phone bricked, since 2.1 sbf will be useless.
Click to expand...
Click to collapse
Overview video of the ota by droidlife revealed the android ver. to be 2.3.15. That is the official OTA. another reason to stay with leaked 2.3.15
Sent from my DROIDX using XDA App

Any news on 2.2

Hi bought my milestone this week and wanted to know about 2.2 update wen it is coming out i checked the phone spec on gsm arena and it said upgradable to 2.2 ? Thanks

delayed again..
suppose to be early Q1 2011 now it Q1 2011.
originally it was Sep 2010.
so, root & install gingerbread from Milestone Development section.

alijs said:
delayed again..
suppose to be early Q1 2011 now it Q1 2011.
originally it was Sep 2010.
so, root & install gingerbread from Milestone Development section.
Click to expand...
Click to collapse
thats the way to go instead of waiting on motorola's lazy ass

byaco said:
thats the way to go instead of waiting on motorola's lazy ass
Click to expand...
Click to collapse
Problem is thanks to locked bootloader we still have to rely on them for a kernel
Hopefully they'll provide us with a good Froyo kernel with the official release, but we'll never get a true Gingerbread kernel

chambo622 said:
Problem is thanks to locked bootloader we still have to rely on them for a kernel
Hopefully they'll provide us with a good Froyo kernel with the official release, but we'll never get a true Gingerbread kernel
Click to expand...
Click to collapse
It doesnt matter anyways. I'm running gingerbread for several days now and it runs flawless. The speed is amazing and the improvement compared to 2.2 is noticeable. You wont be needing a 2.3 kernel. I think the milestone can stay with this. Installing an AOSP Gingerbread + some memory tweaks in open recovery juices the most from this phone. Flash works perfectly! Can it get better than this?
I believe when the minor bugs(mostly unnoticeable) in Gingerbread will be fixed everything is going to be great.
So who cares about motorola anyways?!

may someone kindly explain how is this possible to "run" gingerbread on froyo kernel (as same as it was with froyo running on eclair kernel)?
What exactly do we get by running new OS without new kernel?
What will be better if we would have gingerbread kernel for the gingebread roms?
It would be nice to know why is this, not just how it manifests.

With the froyo leak, a new kernel was released, so there are a lot of ROMs that can replicate froyo performance for real now... and please correct me if i'm wrong but gingerbread is based on the froyo kernel right? so thats why we've already got froyo as well as GB roms for milestone...

if we are lucky end of February, early March official release is to be expected

Yeah froyo will be one your er.. our phone in two weeks.
Sent from my Milestone using XDA App

carthikv12 said:
gingerbread is based on the froyo kernel right?
Click to expand...
Click to collapse
no, there is some difference in version number
btw people writing things like
"in two weeks"
"at the end of the march"
are wild guesses, right? or do you have any background info you can share with us?

MuF123 said:
no, there is some difference in version number
btw people writing things like
"in two weeks"
"at the end of the march"
are wild guesses, right? or do you have any background info you can share with us?
Click to expand...
Click to collapse
Official statements are still in the form of Q1 2011...the rest is guessing. I suggest you root your phone and learn how to flash ROMs. Froyo (2.2) is the end of the line for our phone from Mot...but the community already has 2.3 working.
Sent from my Milestone using Tapatalk

Caz666 said:
Official statements are still in the form of Q1 2011...the rest is guessing. I suggest you root your phone and learn how to flash ROMs. Froyo (2.2) is the end of the line for our phone from Mot...but the community already has 2.3 working.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
I've already had tried almost every rom available for milestone, I just hope that the official froyo release will bring the devs some better ground to build their roms on, isn't that right? Won't be the official froyo release any better?

MuF123 said:
I've already had tried almost every rom available for milestone, I just hope that the official froyo release will bring the devs some better ground to build their roms on, isn't that right? Won't be the official froyo release any better?
Click to expand...
Click to collapse
You are probably right to a certain extent...the kernel and motor drivers are not release/final. But for all we know, the latest leak is final.
What problems remain for you?
The latest android leak has excellent battery life and performance in CM7 is through the roof...
Sent from my Milestone using Tapatalk

Android 3.0 for Milestone?

Hi all develoers here. Salute to you all for whatever you did for our milestone.
Just a noob question. Is by any chance, by stripping down, or by any magic, is there a possibility to port Android 3.0 for Milestone? Is it possible?
http://developer.android.com already released information and sdk about 3.0. Any expert comments about hardware requirement or any hardware comparisaon details available yet?
I have seen many chinese android tablets and devices with same or lower configuration than milestone running with higher versions like 2.3.3 and some even claiming to have 3.0. (There are already many 3.0 tablets on ebay with lower configuration than Milestone. http://cgi.ebay.in/BRAND-NEW-8GB-7-...31243148?pt=IN_PC_Laptops&hash=item4cf532848c )
Any possible luck? Any experts there?

The old HTC G1 even can run 3.0 (just for fun, nothing more) so i think MS can run 3.0 (but...just for fun, nothing more...^_^).

As sayd, maybe MM can run 3.0 with some hack/tweak/mods, but nothing farther...
Google says that 3.0 is for tablets intended, 2.3/2.4 and so on for mobile

MM can't run Honeycomb, cause we have locked bootloader.
I can't imagine Honeycomb with Froyo kernel

keunhuvac said:
The old HTC G1 even can run 3.0 (just for fun, nothing more) so i think MS can run 3.0 (but...just for fun, nothing more...^_^).
Click to expand...
Click to collapse
Then why not for fun? When other low-configured devices can run 3.0 seriously, then why not on Milestone, which actually have good confi?
lvcio said:
As sayd, maybe MM can run 3.0 with some hack/tweak/mods, but nothing farther...
Google says that 3.0 is for tablets intended, 2.3/2.4 and so on for mobile
Click to expand...
Click to collapse
Do you still believe that developers should stick to what google or anyone else said? Most of the new tablets runnung 3.0 have similar configurations and even resolution of milestone.
ovitz said:
MM can't run Honeycomb, cause we have locked bootloader. I can't imagine Honeycomb with Froyo kernel
Click to expand...
Click to collapse
Do not agree. Milestone is already rooted and thousands of experimets with GB is already done. Seems you dont visit milestone rom developement section. Its always better to get some information before commenting with dead ends.
Anyways thanks all for your inputs.

Are they still trying to Bruteforce open the bootloader? Or did they give up?

It's still open at www.androinc.net, but most of us don't trust the project since the source was never released and it just seems shady.

almost a month over, but no useful information from motorola nor any developers. Seems motorola bootloader will never be cracked in future.

indiacam said:
Do not agree. Milestone is already rooted and thousands of experimets with GB is already done. Seems you dont visit milestone rom developement section. Its always better to get some information before commenting with dead ends.
Anyways thanks all for your inputs.
Click to expand...
Click to collapse
You are wrong. All the latest rom available for MM is over froyo kernel and no GB as you stated. Yes we now run GB on our MM but the Kernel still Froyo. I think YOU should start read the DEV section a bit more instead of saying this things.
Peace
Sent from my Milestone using XDA Premium App

Google has clearly stated that Android 3.0 is only meant for tablet use.

Nexus 6 Kit Kat Possible?

This probably sounds like a crazy question, but wondering whether it would be possible to build/run AOSP 4.4.4 on Shamu?
The factory firmware for Shamu is 4.4.4, so it should be possible afaik.
The only reason I can think of for why it wouldn't work is proprietary binaries, as 5.0 are the earliest available.

Q9Nap said:
This probably sounds like a crazy question, but wondering whether it would be possible to build/run AOSP 4.4.4 on Shamu?
The factory firmware for Shamu is 4.4.4, so it should be possible afaik.
The only reason I can think of for why it wouldn't work is proprietary binaries, as 5.0 are the earliest available.
Click to expand...
Click to collapse
Factory firmware for Shamu was 5.0. Thats what it shipped with. Their was never a 4.X for Shamu.
As for 4.4.4, anything is possible. Will you be able to find a dev willing to work on it? Most likely not. Makes no sense other than the challenge of it. Might be a project you can take up yourself if you like. There are tons of tutorials, information, and devs around to give advice.

Q9Nap said:
This probably sounds like a crazy question, but wondering whether it would be possible to build/run AOSP 4.4.4 on Shamu?
The factory firmware for Shamu is 4.4.4, so it should be possible afaik.
The only reason I can think of for why it wouldn't work is proprietary binaries, as 5.0 are the earliest available.
Click to expand...
Click to collapse
sure, its possible.. do you havd a kitkat driver for the n6 to make it work? if not, then itll never work. btw, google never released the drivers.

christianpeso said:
Factory firmware for Shamu was 5.0. Thats what it shipped with. Their was never a 4.X for Shamu.
As for 4.4.4, anything is possible. Will you be able to find a dev willing to work on it? Most likely not. Makes no sense other than the challenge of it. Might be a project you can take up yourself if you like. There are tons of tutorials, information, and devs around to give advice.
Click to expand...
Click to collapse
Yes, Shamu shipped with 5.0, but there is a 4.4.4 factory firmware file that is available for use by repair centers.
I've tried it, and it is a very minimal build. It isn't worth using as a daily driver at all.
I'm sure I could repo sync and compile aosp 4.4.4, but I don't want to take the time and effort if it won't work lol.
Besides the lack of 4.4.4 proprietary binaries, there is also no official 4.4.4 kernel source, so I'm basically wondering if it could work with 5.0 proprietary binaries and kernel source?

simms22 said:
sure, its possible.. do you havd a kitkat driver for the n6 to make it work? if not, then itll never work. btw, google never released the drivers.
Click to expand...
Click to collapse
Right, the lack of 4.4.4 drivers and kernel source are my main concern as far as whether it would work.
I'm wondering whether it would be possible to extract the necessary driver files and kernel from the factory buid?

Q9Nap said:
Right, the lack of 4.4.4 drivers and kernel source are my main concern as far as whether it would work.
I'm wondering whether it would be possible to extract the necessary driver files and kernel from the factory buid?
Click to expand...
Click to collapse
theres no kitkat driver, period. if there is, google has it. no, you cant extract a past driver from a newer os.

simms22 said:
theres no kitkat driver, period. if there is, google has it. no, you cant extract a past driver from a newer os.
Click to expand...
Click to collapse
I have a 4.4.4 pre-release build from Motorola; would it be possible to extract the drivers and use its kernel/boot image?

Pre-release build of what from Motorola? Unless that pre-release build is specifically for the Nexus 6, you won't be able to use its kernel with the device.

*removed*

Q9Nap said:
I have a 4.4.4 pre-release build from Motorola; would it be possible to extract the drivers and use its kernel/boot image?
Click to expand...
Click to collapse
nope. drivers are very device specific. it has to be a nexus 6 driver, or you will not get any of the software to work with the hardware and with the physical device.

simms22 said:
nope. drivers are very device specific. it has to be a nexus 6 driver, or you will not get any of the software to work with the hardware and with the physical device.
Click to expand...
Click to collapse
Ok, I'll say it again; I have official 4.4.4 Motorola firmware for the Nexus 6. See the build.prop in the previous post.
Is it possible to extract the drivers and kernel from this and include in AOSP 4.4.4?
It is factory test firmware and isn't really viable to use as a daily driver, which is why I want to use parts from it to build AOSP.

Q9Nap said:
Ok, I'll say it again; I have official 4.4.4 Motorola firmware for the Nexus 6. See the build.prop in the previous post.
Is it possible to extract the drivers and kernel from this and include in AOSP 4.4.4?
It is factory test firmware and isn't really viable to use as a daily driver, which is why I want to use parts from it to build AOSP.
Click to expand...
Click to collapse
you can try, thats the best that i can say..

As @simms22 already said, you can try it. However, according to the build.prop, ro.product.model is an XT-1080,which is a Droid Ultra. The hardware for the Droid Ultra is completely different from the N6, with specs more applicable to a Samsung Galaxy S3, and thus its drivers and kernel will both be different. Neither will work on the Nexus 6.
I'm sorry, but I highly doubt this is a genuine Nexus 6 pre-release ROM. Posting the build.prop is insufficient proof, as the build.prop can be easily edited to have it say whatever you choose. You'll have to find another way to persuade the audience.

I'm not trying to persuade anyone, lol. I'm just asking whether it's theoretically possible or not.
You are welcome to have access to the full firmware if you like, sheesh.
Why would I bother faking a build.prop?

It's not, as the Droid Ultra hardware is totally different. As to why anyone would want to fake a pre-release ROM, your guess is as good as mine. But at least you provided something when asked, unlike one guy in the S4 forums who claimed he could reset the Knox efuse after it was tripped, something not even Samsung can do.

Strephon Alkhalikoi said:
It's not, as the Droid Ultra hardware is totally different. As to why anyone would want to fake a pre-release ROM, your guess is as good as mine. But at least you provided something when asked, unlike one guy in the S4 forums who claimed he could reset the Knox efuse after it was tripped, something not even Samsung can do.
Click to expand...
Click to collapse
This is not for droid ultra. Yes, one line in the build.prop says xt1080, but everything else says shamu. Apparently, xt1080 was the working model number during testing.
For you and any other doubters, here ya go:
https://drive.google.com/file/d/0B-53iD-71B3iMElKNWdybC1aanc/view?usp=sharing

Wow, this thread is hilarious.
First off, there is no such thing as a driver that is linked specifically to a version of Android. The driver is between LINUX and HARDWARE.
While newer versions of Android may be more demanding of the kernel, they are not intrinsically tied together. You can run Android 2.0 on Kernel 4.6 if you want. Nothing is going to stop you from doing that.
Now the place where you could run into some stickyness, is in the **hardware abstraction layers**. These are not the drivers. These are the bits of code that talk Android API on one side, and Linux on the other side. Most of the HALs are open source, so could be converted if need be.
Most of the HAL changes are things being added into the new versions that didn't exist in the old. As a result, in most cases, you could take a 5.0 HAL and stuff it into a 4.4 system image -- and it should work.
But the big question is.... why would you ever want to do that? 4.4 is obsolete and dead. LEAVE IT BE!

doitright said:
Wow, this thread is hilarious.
First off, there is no such thing as a driver that is linked specifically to a version of Android. The driver is between LINUX and HARDWARE.
While newer versions of Android may be more demanding of the kernel, they are not intrinsically tied together. You can run Android 2.0 on Kernel 4.6 if you want. Nothing is going to stop you from doing that.
Now the place where you could run into some stickyness, is in the **hardware abstraction layers**. These are not the drivers. These are the bits of code that talk Android API on one side, and Linux on the other side. Most of the HALs are open source, so could be converted if need be.
Most of the HAL changes are things being added into the new versions that didn't exist in the old. As a result, in most cases, you could take a 5.0 HAL and stuff it into a 4.4 system image -- and it should work.
But the big question is.... why would you ever want to do that? 4.4 is obsolete and dead. LEAVE IT BE!
Click to expand...
Click to collapse
This is the kind of response I was looking for, thank you!
Yeah I know KK is obsolete; the main reason I am interested, besides theoretical curiosity, is the holo dark ui; really don't like the bright material white ui, and the material dark ui doesn't look that great either.
I know I can use cmte, layers, or substratum to install a dark ui theme, but I haven't found a theme yet that doesn't have issues and/or inconsistencies, and they don't look as good as og holo dark imo.
Anyway, it definitely sounds like more trouble than it's worth, lol.