Database Info

Bought a Nexus One; totally, completely baffled by tethering

I'm a professional programmer, and I'm baffled. It seems that there is a whole "smartphone scene" and it's intimidating. I'm a Java expert and am comfortable with the Android SDK in Eclipse. However I'm completely baffled by the prospect of getting tethering to work on my Nexus One.
One thing that baffles me, for example, is the concept of a "ROM". Is there a ROM on the N1? I thought that ROMs haven't been used for 10 years. I was under the impression that the N1 is basically a little PC running Linux, which means that it should only have a bare minimum of a BIOS and everything else would be on "disk", or flash.
Another thing that baffles me is the concept of "rooting" the N1. It's running Android, which is an open-source mobile operating system. And, as far as I know, I have the permission to change all bits of the phone. Heck, that's part of the appeal! To say that you have to "root" your N1 is like saying that you have to "root" your Ubuntu box - it just doesn't make sense.
Complicating matters is the release of Froyo. I simply don't know enough to judge whether the actions required to upgrade the N1 to Froyo are compatible with the actions required to install a tethering app.
And that's the thing: I'm not just interested in installing tethering. I want to understand what I'm doing and why. I'd like to understand the options choose intelligently between them. There are so many resources online which are trying so hard to be helpful, but which don't really answer these simple questions.
I really appreciate your help.
-Ablation

search the correct forum for your phones model here on xda. some roms provide tethering preinstalled
check this thread for more info
http://forum.xda-developers.com/showthread.php?t=668090
while that targeted at g1, its the same concept. again search xda for the n1 section

Thanks for the link. However, I think I need a more conceptual introduction to the scene. The essential question is: what are the bits? On a PC you have:
1. BIOS
2. Disk
3. Peripheral firmware.
The disk is further broken down:
1. Bootloader
2. Operating system
3. Drivers
4. Applications
When you say ROM I assume you mean some combination of BIOS and Peripheral Firmware?

Hello Gentlemen - Building a ROM? where to start..

Now I'm completely sure that this thread isn't quite the sort of thing that's intended for this Development forum but in this case I'd like you to make an exception as it's intention is for future development and I'm seeking the input from the current great bunch of developers that we have.
I wouldn't mind having an attempt at putting together my own ROM or at least hacking an existing close to stock ROM and making it my own, I have no plans to release my creation to the mass market (if I ever get that far) but, just want to go through the process in order to give me a better understanding of how it all hangs together so that I can put more into the community and assist more in this section and not just the general one with basic problems.
Any pointers that anyione can give will be gratefully appreciated.
I'm not seeking to build a thin Senseless ROM as there are are already some fine examples of these already (MIUI and CM etc), as I'm new to Android and have come here from Windows Mobile so I've already made HTC my choice mainly as I like Sense its functionality, integration, even though I do believe it could be slimmed downed by a decent degree and loose many unnecessary components and elements from the start. I'd also like to only build a WWE ROM as it would be intended for just my use.
As you may know already or can see from signature (or my many previous posts) my current favorite custom ROM is LBC so I'd like to have a go at creating my own version of something similar, I'll probably only end up using LBC still as my daily ROM as I've loved it since I first moved to it and have no intention of going elsewhere.
I have JDK and ADK installed on both my PC's, I've been a programmer although quite some years ago, but, still have a reasonable amount of IT knowledge and still work in a IT related job. So configuration, UNIX scripting etc isn't a problem although Java programming may well be!
Just looking for some basic pointers even if they are to websites or resource threads here in XDA for further reading. Many thanks for all the pointers offered and any time spent helping me, I'm also sure that anything you guys put together will then prove useful for others if they are in my position.
I've also very recently just done my back in and am suffering from awful sciatica, so can see myself spending some time off work, bizarrely sitting at the computer on certain chairs for medium lengths of times, is one of the few things that I can do without experiencing much pain, so I'm trying to keep my self busy, amused and avoid (further) insanity so this seemed like the best option!
Thanks in advance (again) I appreciate that the people in this forum are exceptionally busy, what with their own life's, their families, their jobs not to mention their relentless dedication to the cause that is Desire S ROM porting and development!

You need first to set up a Linux environment.
1. For personal use, and only for modding, I recommend you installing Cygwin if you are a Windows user.
2. Download Dsixda Kitchen and follow the steps from there.
3. Get a copy of your favourite ROM, or a base of your ROM in a .zip format.
4. Modify it, tweak it, zip it again and enjoy !
If you have any more questions, I am here to answer them.

badeaioan said:
You need first to set up a Linux environment.
1. For personal use, and only for modding, I recommend you installing Cygwin if you are a Windows user.
2. Download Dsixda Kitchen and follow the steps from there.
3. Get a copy of your favourite ROM, or a base of your ROM in a .zip format.
4. Modify it, tweak it, zip it again and enjoy !
If you have any more questions, I am here to answer them.
Click to expand...
Click to collapse
Genuine Question: (Not one of those how fast is your PC ones?....But)
At home I have a very new i7 laptop running windows 7 - 64 and a just under ten year old dual Xeon based workstation still running XP both with 8Gb. which of the two would be the best base O/S machine for creating the linux environment on? I imagine that the new laptop will have much fast CPUs but the workstation has many more faster SCSI disks. Although both have NAS available storage.

It doesn't matter. It's your choice. For example I have only Win7 32-bit both on PC and Notebook. I also have native Ubuntu on Notebook as a dual boot, but I use it only on modifying apps.

I never used the kitchen to make own rom, but its the fast way
and you can run linux on a virtual machine if you want

superkid said:
I never used the kitchen to make own rom, but its the fast way
and you can run linux on a virtual machine if you want
Click to expand...
Click to collapse
I'd seriously appreciate a LINK to a linux disto VM that I could download and get started with. As I'm currently starting with an empty page!?
What O/S or linux flavour/distro do the other chiefs use (a URL or link would be magic)?
LBC?
MaryLandCookie
proxuser?
superkid?
NeoLojik?
(dont feel bad if I missed you out - we've finally too many Cooks to remember!)
etc
As always any assistance much appreciated.
and regarding the Development INDEX thread -I've heard back from the MOD but am still awaiting him to action the change of owner for the thread. SO post any needed updates or ideas into the thread and I'll action them as soon as I can!

Ben, start with this, you won't need anything else for personal use: http://forum.xda-developers.com/showthread.php?t=633246
You will find out here how to set up Cygwin and everything else you need.

Virtual machine here
Linux distro
Use with dsixda's kitchen, you can't go wrong. Although I prefer dual boot.

lol i use debian, but i dont have a vm

superkid said:
lol i use debian, but i dont have a vm
Click to expand...
Click to collapse
I don't use vm myself, but for those not wanting to make big system changes a vm is a good way to go. Never did like cygwin either, but its all about personal preferences I guess
Sent from my HTC Desire S

ben_pyett said:
Now I'm completely sure that this thread isn't quite the sort of thing that's intended for this Development forum but in this case I'd like you to make an exception as it's intention is for future development and I'm seeking the input from the current great bunch of developers that we have.
I wouldn't mind having an attempt at putting together my own ROM or at least hacking an existing close to stock ROM and making it my own, I have no plans to release my creation to the mass market (if I ever get that far) but, just want to go through the process in order to give me a better understanding of how it all hangs together so that I can put more into the community and assist more in this section and not just the general one with basic problems.
Any pointers that anyione can give will be gratefully appreciated.
I'm not seeking to build a thin Senseless ROM as there are are already some fine examples of these already (MIUI and CM etc), as I'm new to Android and have come here from Windows Mobile so I've already made HTC my choice mainly as I like Sense its functionality, integration, even though I do believe it could be slimmed downed by a decent degree and loose many unnecessary components and elements from the start. I'd also like to only build a WWE ROM as it would be intended for just my use.
As you may know already or can see from signature (or my many previous posts) my current favorite custom ROM is LBC so I'd like to have a go at creating my own version of something similar, I'll probably only end up using LBC still as my daily ROM as I've loved it since I first moved to it and have no intention of going elsewhere.
I have JDK and ADK installed on both my PC's, I've been a programmer although quite some years ago, but, still have a reasonable amount of IT knowledge and still work in a IT related job. So configuration, UNIX scripting etc isn't a problem although Java programming may well be!
Just looking for some basic pointers even if they are to websites or resource threads here in XDA for further reading. Many thanks for all the pointers offered and any time spent helping me, I'm also sure that anything you guys put together will then prove useful for others if they are in my position.
I've also very recently just done my back in and am suffering from awful sciatica, so can see myself spending some time off work, bizarrely sitting at the computer on certain chairs for medium lengths of times, is one of the few things that I can do without experiencing much pain, so I'm trying to keep my self busy, amused and avoid (further) insanity so this seemed like the best option!
Thanks in advance (again) I appreciate that the people in this forum are exceptionally busy, what with their own life's, their families, their jobs not to mention their relentless dedication to the cause that is Desire S ROM porting and development!
Click to expand...
Click to collapse
Well in my opinion you are alone here because i dont know what the level here it is that anyone helps someone who dares to port a rom. Like i think i am from a specific country or dont know what only few are here who helps me in porting a rom otherwise all have a very good excuse that he is not ready to help anyone. I would like to mention the names who help me in porting the rom and they are mike1986 and one of his team members otherwise majority are here in a race to become number 1 in a specific forum etc. So brother try to see the above mentioned tutorial of how to port a sense rom and try yourself otherwise i had a bitter experience.

This is an excellent place to start, some excellent support from dsixda, dastin1015 among others.
Basically with their help I built my first AOSP ROM for the DS and further.
Well worth a look.
Peace

Just one thing, AOSP means compiled from cm or Google source. Actually it's not possible to compile from Google sources only from CM.

trismegistos said:
Just one thing, AOSP means compiled from cm or Google source. Actually it's not possible to compile from Google sources only from CM.
Click to expand...
Click to collapse
Android Open Source Project to me is google, without sense or any other "knobs". You can compile a pure rom from these sources, I produced one with help from members on other forums.
Getting it to work fully is another matter, lol.
It's definitely an easier route - but none less valid - to take a stock rom & tweak it with dsixda's excellent kitchen.
Sent from my HTC Desire S

Is there an easy way to change things like default wallpaper, desktop icons, widgets layout and so?
I've been reading and using kitchens but can't find the answer

fosco_ said:
Is there an easy way to change things like default wallpaper, desktop icons, widgets layout and so?
I've been reading and using kitchens but can't find the answer
Click to expand...
Click to collapse
try uot kitchen
http://uot.dakra.lt/
its quite easy to use
you can read this guide to get started

[Q] Question on Android SDK

Hello, guys.
Let me tell you a little bit about myself: I'm a software and hardware enthusiast. I have lots of experience slimming down operating systems, including iOS, BlackBerry OS, and Windows itself (I'm pretty proud of my knowledge to tell you the truth). However, I don't know squat about programming. I have very little experience with Python, but nothing else.
Not until recently was that I first had an Android smartphone under my property (3 days ago to be accurate), and I've been playing around with it this whole weekend. So far, I've managed to unlock the bootloader and root the phone (a Moto G, by the way) without installing any other ROM. Not bad for my first time, is it? Anyway, now that I know stuff as "simple" as that (took me a whole day to accomplish them), I want to take the next step: installing a ROM.
I downloaded the Android SDK, and I realized it contained a system.img file. I know that image is generic, and you're supposed to custom it according to your needs, but my questions are: if I install the untouched system.img file to my device, is my device going to work? What are the risks of doing that? Would I need to integrate my device's drivers in order for the image to work, or many more things than just integrating drivers? And, most importantly, is that file what you guys call a "pure Android (or AOSP)"?
Thank you very much.

[Completed] Need a lot of help with porting GB

ok, first, I'm disabled, in a chair, on the dole, and DIRT poor. This is pertinent because it means I can't afford a better device, I have to work within my means. Suggestions to upgrade my device will be ignored. Second, I use Windows, mostly. I CAN use Linux a BIT, but don't really want to, as it's not very intuitive or user-friendly, and my current PC hardware configuration has a LOT of difficulty running even the newest Linux distros. I consider myself pretty computer-savvy, been a freelance PC tech for 20 years now, so I've got some fairly advanced skills and knowledge. I think. I'll also say that my phone is rooted, and has CWM recovery installed.
What I need help with is porting my current rom, to remove ALL of the PHONE/SMS features, and ALL of the wifi power-saving features built into Android. Basically, I want it to function as a non-3g tablet, but with MAX WIFI. GPS would be nice, I use Maps and Navigation a lot, but is not REALLY necessary, as long as I can use a wifi location, Maps should work fine. Since my device is plugged in most of the time, I don't need power-saving features, and I'm pretty sure that THEY are why my device is constantly "disabling" my wifi network (wifi shows as available, 2 bars (-60 or -70 dBm, never seen more than -76) BUT labelled "Disabled, secured with wpa/wpa2 psk. KNOWN issue with GB, I'm pretty sure.) If I click connect, it works FINE. while I'm using it. but after about 10 mins, it's disabled again. Googling this problem has led me to the belief that it is the unwanted power-saving features that are doing this. I should say that I have a KILLER battery my brother gave me, at present I can go 3 days without a charge, and that's with music playing 24/7 over a bluetooth connection, max brightness, AND using wifi/tethering as much as I can. So battery life is not a problem.
I do NOT have access to the SOURCES for my rom. I emailed Huawei and asked for them, and was given a link to the stock firmware, which is in some kinda strange format (it's an .app file, and I can't open/edit it, merely install it. If I could unpackage it, I MIGHT be able to use IT as a source, but I doubt it.)
I can do the work, it's surprisingly easy. I am currently running a kernel that I compiled, but this is beyond me. I have a Linux partition runnin 14.04 LTS. What I need from you:
what programs to use? where to get them? Instructions on HOW to USE them written for somebody who knows JACK about Linux. I ca ./run_a_Program, and have SOME knowledge about repos/sources and compiling/cross-compiling.
and the BIG part is: WTF do I remove/change to accomplish this? PLEASE, if you are replying, remember that I'm an idiot about this stuff, so K.I.S.S.
I have read ALL of the "noob-friendly" guides available here, and they all have one fatal flaw for me: they tell you HOW to do stuff, but not WHAT to do. They setup a build environment, and say have fun. WTF? IDK what im doing, here. What does Demilitarized_zone_free_space=2048 mean? what does changing it affect? how do I change anything, given that IDK What any of this MEANS? Think of it like this: I grew up racing hotrods, know EVERYTHING about them. Now I'm trying to work on an electric-only car. A LOT of my knowledge is useless, but I HAVE already managed to mod a buncha stuff, so I have SOME learning.
I don't REALLY wanna spend YEARS learning Linux, just to tweak my phone. I know I'm gonna have to USE it to do what I want, that's fine. where to start?
And if there is some SIMPLER WAY to do this, I'd LOVE to hear it. I ran across an apk one time here on XDA, that solved the wifi issue, but I cannot find it now.

Hi!
I can understand your frustration. Have you tried asking in the guide threads that you've referred to? Seems the best place to ask questions to me.
Have you seen this guide?
> Android Development and Hacking > Android General > [GUIDE] How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs [Update: Sept.25.2012
It's an old thread, but still some recent activity in it. Or ask in any of the other threads you spoke about reading.
You could ask for help here as well,
> Android Development and Hacking > Miscellaneous Android Development
Hopefully you can find help in one of these places!
Good luck!

[Firefly] [ROCKCHIP] [ITX-3588J] ITX-3588J ARM Android/Linux Dual "Deskphone" Progress

First off, I wanted to say I posted a few threads about this thing here asking questions about stuff I needed to get it working in the way I'd like and I'd want to thank you because I have made a lot of progress in getting it to be what I'd like it to be. I also don't know if this is the best forum to post this report because it's neither a question nor necessarily a tutorial but rather a summary and description of work already done so far, and especially because this device, while it sure runs Android (very well!) does not fit into any of the categories on this site neatly.
The story so far
This post concerns my experience working with the ITX-3588J, a board released just a few months ago by the Chinese manufacturer Firefly (or T-Chip Intelligent Technology Co. Ltd, based in Zhongshan) that is in the coveted mini-ITX form factor which means it can actually fit into a small-size desktop computer case and indeed has enough compute power to theoretically - and perhaps not so theoretically! - function as an honest desktop system with an ARM processor: namely the - also very new - Rockchip RK3588 system-on-a-chip.
About two months ago, I was looking into acquiring a new kind of computer to replace my somewhat longer on the tooth x86 machine that would be compact, low-power, and easy to transport while also being a fully capable desktop. And I certainly didn't want Apple. I had seen some very small form x86 desktops before, but I also knew there were many boards - like Raspberry Pi - that featured the ARM processor. Not content with the Pi, which is still very weak for this application at least when compared against modern software, I wanted to see if there was something else by now in a similar vein, and when I saw this board I thought it was an amazing option, esp. given I have not yet found a peer. Many ARM single-board devices exist but this is the only one I've found so far that looks to be in a proper desktop form factor and sporting a processor powerful enough to work at that level.
So I got the board, a case, and - noting it had SATA ports - a cheap 250 GB SSD, and put it all together ... and fired it up! And to my surprise, it booted up Android! Which was a real shocker because I generally thought this'd be like another PC board, not having had much experience with this ecosystem beyond phones, so that it would just give the usual "OS not found" stuff. Nope - pre-loaded on the board. Very minimal, very bare-bones though, not even the Google Play and similar essentials required for a usable Android experience. Yet with the little bit I had, I couldn't help but notice it was extremely fluid, responsive, and snappy, moreso than my aging 2018 era x86 box. Moreover, it was very, very interesting (and exciting!) to see Android booted onto a full-size monitor screen like Linux or Microsoft Windows - and actually and surprisingly, to see that it didn't look and feel all that bad!
However, of course, I wanted more. First, I wanted a fully-featured installation of Android. Second, I wanted to run Linux on it - especially given that, a short while later, I found that the board manufacturers were offering a stock Ubuntu 20.04 to be installable to it. Although, in the early stages, I didn't know how to do this at all, and then soon after learned how to reflash the embedded MMC chip to change the OS. And I did so, trying the Ubuntu and finding it also very performant, but not liking either that it was not quite the newest version but also more that it was mutually exclusive with Android - so far.
And that would begin a long - and at many times frustrating, especially given how much information out there is not at all tuned to a device like this being pressed into this application - learning journey toward exploring topics as diverse as how ARM processors and SoCs work under the hood, U-Boot, kernel features, the Firefly-Rockchip developer kit - and having to essentially single-handedly discover many of that kit's ins and outs given there was pretty much no documentation - and more, ultimately leading to where I've got it to now.
What it can do at this point
And that is, right now, I have it sitting here, loaded up with the stock Android 12 and Ubuntu 20.04 - with the former on the eMMC and the latter on the SSD hard drive. On the Android side, Google Play is now loaded and functional, though Google Chrome is not (it crashes with a "Telephony is null" exception for some reason, which seems to suggest for some reason it's trying to act like it's on a phone but isn't). Zoom - an app that I really, really wanted to have (and why I wanted to keep Android around on it) - works and works smoother and cleaner than my 2018 x86 Linux clunker. On the Ubuntu side, though, things are not yet coming - mostly because of seeming inability to use U-Boot to boot from the SSD. I managed to install GRUB, and given that Firefly's generous board SDK provides the full U-Boot source code was able to recompile it with the necessary "bootefi" command enabled which is not present in stock, but nonetheless alas this U-Boot seems to have its SATA support bugged or incomplete, because it would crash immediately upon trying to initialize that subsystem.
Where I'd like to go with it
Obviously, full dual boot of Android and Ubuntu, so getting U-Boot to boot the GRUB resident on the hard drive, is the biggest issue so far, and that means investigating whatever is the problem (or not?) in its SATA subsystem. Getting Google Chrome working on Android is another important step. Moreover - though it would cost extra money that I do not have right now - there's the very interesting possibility, owing to the fact that it has a built in M.2 slot on the board, and alluded to in the title - that the device could be made to act as a cell phone. And finally, the possibility of upgrading to a newer version of Ubuntu (ideally 22.04) - however from what I know so far, it looks like this will have to wait because the stock Linux kernels do not currently support the RK3588 fully - though I'd suggest the Linux kernel developers really should take a look at the SDK that came with this thing because it has lots of code in it including for the kernel, all under GPL.
Final note
One of the most interesting things I've learned from this project, and mentioned earlier, is just how well Android seems to work as a desktop OS. While there have apparently been some attempts to port it to x86, this is perhaps one of the first devices that is desktop-workable and which runs it natively. And one of the things I find that's nice about it is that ironically, because all the apps are designed for small screens, when they are run on a very big screen (and this monitor is not "very big" even by today's monitor standards, being a used and earlier LCD type), they are extremely easy on the eyes and have minimal UI clutter when compared to a typical desktop app on most Linux WMs and on MS Windows.
If you want to know more about the details, or anything else, feel free to ask any questions you might have!

UPDATE:
I believe I may have found an easier way to dual-boot Linux with Android, and that consists of configuring a custom ROM that will put both kernels, and GRUB, on the board's eMMC, while the rootfs for both OSes is placed on the hard disk. Will be seeing how it works.

UPDATE:
I have almost completed the custom ROM! I have now both Android and at least the base system for Ubuntu 20.04 (Kernel 5.10.66) bootable with Android now storing user data on the hard drive; though I'm still running into some hardware initialization issues in the latter that are keeping me from actually installing the desktop system. With regard to the Ubuntu system, there is some interesting issue in that for some reason the provided SDK kernel, which I had to rebuild, seems to build more Android-like because it wants to look in "/vendor" for some things related seemingly to the networking facilities, and it is possible this is preventing me from bringing up wifi, which I need in order to download the rest of the system.
But lots of progress overall - it seems that a full-fledged ARM desktop running simultaneously Android and Ubuntu is within reach to be wrung from this board!

Ignore my request for an update in another post. Seems you like you moving along. I don't need dual boot, just a working Android 12 with GPlay and Chrome. Did you get Chrome to work?

mebalzer said:
Ignore my request for an update in another post. Seems you like you moving along. I don't need dual boot, just a working Android 12 with GPlay and Chrome. Did you get Chrome to work?
Click to expand...
Click to collapse
Thanks. Yeah, I want to say that I have pretty successfully gotten Android 12 working on it for sure, but Ubuntu is proving much more difficult due to graphics support issues, and I'm not sure if it will be possible until RK3588 is supported in the mainline Linux kernel tree which is still something under development. And yes! I got Chrome to work Everything works, actually - it's great as an Android system, though obviously Android is kinda funny to use as a desktop OS. I am wondering if I can't get a "pseudo" Linux using something like Linux Deploy in lieu of running it natively, at least until the kernel development catches up with this new processor.
(FWIW, I'm posting this post from that machine while it is running A12. )
Good to see someone else is interested in it, though. What are you planning on using yours for?

Insofar as getting Android 12 to work w/GApps - it depends on if you want to do it purely on the eMMC or you want to also put user data on an attached hard drive like I did. In either case, the best option, I feel, is to create a custom ROM - I could provide custom ROMs for it for download, but don't know because of Google's licensing conditions around the GApps and have heard of people getting in trouble with Google for distributing custom ROMs for phones that have GApps in them. You basically need to unpack the stock Android image, unpack the "super.img", then load the apps from a package like NikGApps into the "product" partition (NOT "oem" - that was a big mistake), then repack everything and flash to the eMMC again. You will need the board SDK from Firefly for all this as it has the custom ROM-packing and flashing tools.
Alternatively, it is possible to manually install the NikGApps GApps using the Android console - as it's a fully unlocked system, obtaining root access is trivial: just put it into Developer mode and you will find the root access in the "Developer options..." menu under "System".

Shimmy99 said:
Insofar as getting Android 12 to work w/GApps - it depends on if you want to do it purely on the eMMC or you want to also put user data on an attached hard drive like I did. In either case, the best option, I feel, is to create a custom ROM - I could provide custom ROMs for it for download, but don't know because of Google's licensing conditions around the GApps and have heard of people getting in trouble with Google for distributing custom ROMs for phones that have GApps in them. You basically need to unpack the stock Android image, unpack the "super.img", then load the apps from a package like NikGApps into the "product" partition (NOT "oem" - that was a big mistake), then repack everything and flash to the eMMC again. You will need the board SDK from Firefly for all this as it has the custom ROM-packing and flashing tools.
Alternatively, it is possible to manually install the NikGApps GApps using the Android console - as it's a fully unlocked system, obtaining root access is trivial: just put it into Developer mode and you will find the root access in the "Developer options..." menu under "System".
Click to expand...
Click to collapse
Thanks I will keep this in mind. See my reply to you other reply on another post as well.

I would to run gplay as well please send me instruction the nikapps github doesnt say nothing