Database Develop

[Q] "Brainstorming" SLCD support.

Dear developers,
i hope it is not too offensive, if so it's not my intention, but is there a way to make all your great ROMs compatible for nexus one SLCD!
Maybe you can share in this thread and it will make the development of compatible ROMs easier for you.
Many people would be happy about it.
Having a compatible recovery with RA RECOVYER 1.8.0.1 is more than just the first step.
Unfortunately I can not help you much, because i'm just consumer and no dev.
The issue is that after flashing several ROMs on SLCD the screen after the first splash screen stays black.
CM 6.0.0 is working after changing the update script before flashing.
I want to enjoy the great variety of your ROMs on my nexus one, so please try to help.
Thank you very much for your great work....!

I would just like straight answers.
Does SLCD support just require updated drivers?
Aren't the drivers included on AOSP?
And therefore, any ROM that draws straight from AOSP has the correct drivers?
Is it easier to install a custom ROM that supports SLCD if you have unlocked your bootloader?
Why is amon_RA 1.8.0.1 the only one that supports SLCD?
Why isn't 1.8.0.1 the most recent version available in the amon_RA recovery thread? And not the most current one listed in ROM manager?

You sound like someone owes you something. Which isn't the case.
Yes, updated drivers. Residing with the kernel, meaning updated kernel.
Yes, included in AOSP. Different tag/branch.
Which means - code needs to be imported/switches set/something else done. Not 1-minute job.
Bootloader doesn't matter. Not easier, not harder - just the same. It's done through recovery anyway.
Because Amon_Ra bothered to make one that supports SLCD.
Because there is a separate thread for it, and if you'd bother looking at the Nexus Wiki in Recovery section - you'd find it there, together with the note to flash it for SLCD. ROM Manager doesn't support SLCD, and in fact most, if not all, cases of "I flashed something and now I have a black screen" as of lately come from those that use ROM Manager. Why doesn't it support? Because it wasn't updated to support. Good reason not to use it and do things manually, at least until it starts supporting SLCD.
CM6 has SLCD support, Enomther is working on adding it, the rest of the devs are probably working on it too.

Jack_R1 said:
You sound like someone owes you something. Which isn't the case.
Yes, updated drivers. Residing with the kernel, meaning updated kernel.
Yes, included in AOSP. Different tag/branch.
Which means - code needs to be imported/switches set/something else done. Not 1-minute job.
Bootloader doesn't matter. Not easier, not harder - just the same. It's done through recovery anyway.
Because Amon_Ra bothered to make one that supports SLCD.
Because there is a separate thread for it, and if you'd bother looking at the Nexus Wiki in Recovery section - you'd find it there, together with the note to flash it for SLCD. ROM Manager doesn't support SLCD, and in fact most, if not all, cases of "I flashed something and now I have a black screen" as of lately come from those that use ROM Manager. Why doesn't it support? Because it wasn't updated to support. Good reason not to use it and do things manually, at least until it starts supporting SLCD.
CM6 has SLCD support, Enomther is working on adding it, the rest of the devs are probably working on it too.
Click to expand...
Click to collapse
Do you know which branch in the AOSP includes support for Nexus One SLCD?
I've already tried the froyo branch without any success and android-2.2_r1.1 branch crashes while flashing.

Didn't check the commits since looking for a way to change MMS resolution (and didn't look beyond that ), so I'm sorry, but I'm not the person qualified to answer. Asking someone from CM team or Enomther might be a better idea to find the Google source (since those ROMs have incorporated the support).
Enomther is basing on r1.1, so it should be usable. Never tried to compile myself, so I can't be of help there....
CM has this commit in his github (from pershoot's log):
87f604b7d75e77af62a2074e993a91aa00f1fcf5 ([ARM] mahimahi: add support for Sony TFT panel)
These are 4 repositories that might also hold the commit:
http://htc-linux.org/wiki/index.php?title=Kernel#Qualcomm_QSD8xxxx

[Q] Samuaz's ICS ROM vs texasice's ICS ROM?

Which ROM is better?

I don't know for sure, but it seems that samuaz's is texasice's build plus the CM goodies. So I would say samuaz's has more features.

bassmadrigal said:
I don't know for sure, but it seems that samuaz's is texasice's build plus the CM goodies. So I would say samuaz's has more features.
Click to expand...
Click to collapse
Ok. Hey, aren't you that Cyanogenmod moderator?

That'd be me

why ask--try them both--

Am using texasice's ROM since like day 1 and loving it. Its my daily driver

I tried thrice to use texacise ROM [Alpha 8, ev-1, and latest p3]. There are huge improvements and p3 is quite close to be used as daily rom. However, still there are issues with network dropping off , random soft reboots and many Apps FCing.
Nexy has good future with both these ROMs progressing so fast [it is less than 50 days since google released the code].
The samuaz ROM, looking at the feedback, I'll give it a try for couple of days next week.

Yes I do notice those soft reboots with p3. But no FCs and no network drops. However the progress for each build looks quite promising.

Would be nice if Samuaz too release a mini skirt version for stock Hboot

Yet another reason not to stay on stock Hboot: Camera is already working (not completely) on N1.
Also msm kernel 3.0 is ready. Just a few days before we get ICS beta

Where can we get the msm 3.0 kernel?

JoshX said:
Where can we get the msm 3.0 kernel?
Click to expand...
Click to collapse
Where? From a kernel dev, of course.
When? When it's ready. Further questions will not aid in getting it faster.
I heard the kernel dev over at the Desire forums is going to upload his msm-3.0 sources to guthub and will make it work on the HD2 and Nexus One, of course after it works on the Desire itself.
Just wait patiently and it will be here sooner or later.

Which rom work on 2g network?

Mohamad_j said:
Which rom work on 2g network?
Click to expand...
Click to collapse
I think texasice's ROM works with 2G network.

Theshawty said:
Where? From a kernel dev, of course.
When? When it's ready. Further questions will not aid in getting it faster.
I heard the kernel dev over at the Desire forums is going to upload his msm-3.0 sources to guthub and will make it work on the HD2 and Nexus One, of course after it works on the Desire itself.
Just wait patiently and it will be here sooner or later.
Click to expand...
Click to collapse
That's what I figured, but it seemed to be implied, by indiangeek, that one was already available.

I just upgraded from CM 7 to Texas ICS p4. The market didn't work (my apps didn't auto-sync and re-download - couldn't get it working after an hour of trying), the animations were a little jerky, camera didn't work, USB mass storage didn't work, CM mods weren't there. In it's current form, it could use a little polishing.
I tried Samuaz's MeDroid ICS 4.1 and it works way better. No market issues. Animations are much more fluid, camera works (panorama and video are broken). Gallery doesn't pull in picasa web albums (that'll be fixed today in 4.2). Also, you get CM features, which aren't present in TICS. I got a few force closes, but I think that was due to not rebooting after restoring from mybackup root, as I haven't had the FCs in a while. Oh, and USB mass storage is working, so I can restore apps and data from my backups. Sometimes the USB icon shows up or the app starts up (like at startup) when nothing is plugged in. Minor issue, though.
Upgrade method (some of these flash files aren't signed, so I needed to disable signature verification before they'd flash):
Upgrade bootloader (HBOOT) to 0.35.0017
Flash latest radio (5.12.00.08) - CHECK THE MD5 BEFORE FLASHING
Install Blackrose using the automatic method (It will not work without the HBOOT above)
Install custom blackrose from http://forum.xda-developers.com/showthread.php?t=1366897 - this increases the space available for ICS to install
Use recovery to do a full wipe three times (people had issues only wiping once)
Mount SD card via recovery and deleted/backed up everything.
Flash Evervolv-Perdo-2.1.0p4-passion.zip from http://forum.xda-developers.com/showthread.php?t=1366897
(Realize a bunch of things weren't working)
Use recovery to do a full wipe three times (people had issues only wiping once)
Flash MeDroid 4.1 from http://forum.xda-developers.com/showpost.php?p=21093710&postcount=188
To do yet:
Upgrade as soon as 4.2 comes out to fix gallery - I'll probably just use adb to replace the current gallery app - http://forum.xda-developers.com/showpost.php?p=21097768&postcount=191
Replace MeDroid's boot animation with this one http://forum.xda-developers.com/showthread.php?t=1429308

Am I the only one to be a little knee-shaking when it comes to flashing radios? I mean, ****ing up the system or boot seems easily restorable, but flashing a corrupted or unsigned radio may turn your device into a fully usable paperweight?
That's kinda the reason I've stayed with the 5.08.00.04 or what it's called. I mean, it works for me and hasn't bugged in any way, so why upgrade it?

I agree it's scary, but I saw so many people using the same file without issues, I was alright with it. Radios are the only file I check md5 on for this reason.

I think you're ok if fastbooting the img and like loki980 said, checking md5
I've done it a few times with no issues

Theshawty said:
That's kinda the reason I've stayed with the 5.08.00.04 or what it's called. I mean, it works for me and hasn't bugged in any way, so why upgrade it?
Click to expand...
Click to collapse
In all my time in the CyanogenMod forum (which is probably waaay too much time), it seems that the 5.08 is the best supported radio with the N1. I have never seen issues fixed from going from the 5.08 to the 5.12, but I have seen quite a few fixed doing the reverse. A lot of people get great results with 5.12, but it seems that more have better luck with 5.08.
Plus, I am sure that Google did a lot of testing before they sent out the Gingerbread update, and I'd bet there is a reason they included the 5.08 instead of the 5.12.

[Q] Can't build CM6 from sources. Help please!

Hi,
I'm trying to build cyanogenmod 6 (froyo) from sources on github for G1.
Sidenote. The reason I'm trying to do this is i'd like to modify kernel parameters. I'm trying to make the phone talk to external device using built in serial port. I can do it with my current CM6, but it looks like serial debugger engages and starts responding to the device and also steals some of the data being sent to phone.
To build I used instruction posted at cyanogen wiki "HTC Dream & Magic: Compile CyanogenMod (OS X)" which covers gingerbread but checked out froyo-stable branch at first. I know that gingerbread version stopped supporting G1 at some point last year.
Without much success even after fixing manifest to point to updated repo urls from kernel.org to googles repo etc. The problem is that apache-http seems incompatible with old sources and it is referenced by head.
I also tried froyo branch, but it doesn't build as well because something seem to be broken for dream_sapphire, and it is not present in the devices anymore.
I've tried searching for compilation errors, and general build questions/instructions here and on cyanogen's forum, but looks like CM6 is not very active these days.
Can someone point me into right direction where to search for relevant info on building it? Would getting a proper revision help or should I combine stuff from several branches to make it work?
I've already spent quite a lot of time figuring out how build is being configured and how things stitch together but without much progress on the actual build.
And with times required to sync a whole repo and build it, it is becoming frustrating.
Any help would be muchly appreciated!
Regards,
Oleg

It's dead.
I also wanted to make a cm6 rom, but I couldn't get anything to work.
I got the addresses all updated but it looks like a bunch of the files have completely dissappeared. You may be able to make it skip those, but then it may not work completely.
Go for AOSP?

Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.

aliher1911 said:
Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.
Click to expand...
Click to collapse
Nope AOSP is as easy to build now
Go to the android site and follow directions
Google for "build android"
At the part when doing repo init you need to get the right branch
Go to "build for devices" then scroll down for recommended branches and look for the dream
One thing you'll need to do differently is do "make otapackage" instead of plain "make"
And once that's done you'll need to tweak the zip and get rid of the "recovery" folder and tweak the updater-script
Oh yeah, and I don't know exactly how you would do this part, but you'll need to get the source for a newer kernel in there, like ezterry kernel and use it with 2708+ radio/spl
Unless you wanna use the AOSP kernel & spl & radio which is old
What I did is just flash his kernel after the rom, but you want to do kernel stuff so yeah...
Sent from my HTC Dream using Tapatalk

Since nobody seems to check the Q&A forum [Q] Kernel compiled in Ubuntu 12.04 fails

Since nobody seems to check the Q&A forum [Q] Kernel compiled in Ubuntu 12.04 fails
So i havent worked on a kernel in a while and decided id start workin on one again. Well I recently updated to 12.04 lts and no changes to my old source I just did a test compile and it wont boot. Same toolchain, source, ramdisk, etc.
Is there some sort of issue with compiling on 12.04?
Even redownloaded the source from my github and tried the toolchain recommended by samsung, stock tool chain, and 3 others and i still get nuthin. Just trying to compile a 2.2 kernel for the vibrant. No source i download works am i missing something?
does ANYONE have any ideas? I dont care who you are just something! I been at this for a freakin week and cant figure it out, ......i've changed nuthing but the OS and i really dont want to have to redo my entire setup because it is such a huge pain

Are you sure the kernel works? What is causing it to not boot?
I build ICS kernels just fine.
Check this and update tools for 12.04 http://source.android.com/source/initializing.html

trailblazerz11 said:
Are you sure the kernel works? What is causing it to not boot?
I build ICS kernels just fine.
Check this and update tools for 12.04 http://source.android.com/source/initializing.html
Click to expand...
Click to collapse
100% sure it works, its the same source as my old nightly# 3 kernel which i can flash and works fine. Its a 2.2 kernel so thatd be the main diff there, and I've already done the setup of the build environment. I dont get past the vibrant logo so i have no idea what the problem is >.< its driving me nuts
i tried the linaro TC, 2 diff code sourcery, google toolchain even, and no luck
I even started a fresh kernel from scratch and added just the EXT4/voodoo stuff and my ramdisk and still nuthin
so i remade my voodoo ramdisk and that still doesnt work.
I'm out of ideas, I've quadruple checked to make sure all my tools and erthing are installed......idk what the issue is

Not a developer but wouldn't downgrading to an older Ubuntu fix the problem? Btw I loved your gingerbread kernels and I hope you can get back to the top again Aim for 400mb ram with 720p and you will achieve something high

helikido said:
Not a developer but wouldn't downgrading to an older Ubuntu fix the problem? Btw I loved your gingerbread kernels and I hope you can get back to the top again Aim for 400mb ram with 720p and you will achieve something high
Click to expand...
Click to collapse
Id rather not but it seems that might be the case -_- I gotta look into how well older versions of ubuntu suppport the BullDozer cores before i do i guess.....
also I only made GB kernels for the NS4g i think ? o .o Vibrant I had been workin on it but I like being able to have MSAA in my games and what felt like greater stability, so i scrapt the new projects in favor of specific features i use :3

Ecotox I really wish you or another dev could make an updated CM7.2 kernel with Voodoo Color, OC/UV, and performance tweaks since Glitch is outdated and probably won't be updated for CM7.2. I know most devs have gone to ICS kernels, but CM 7.2 is still snappier and better for gaming then ICS.

hurtz777 said:
Ecotox I really wish you or another dev could make an updated CM7.2 kernel with Voodoo Color, OC/UV, and performance tweaks since Glitch is outdated and probably won't be updated for CM7.2. I know most devs have gone to ICS kernels, but CM 7.2 is still snappier and better for gaming then ICS.
Click to expand...
Click to collapse
I've been gone working on a game project, so I really haven't been doing much android stuff in months. If I get some time I might but can't make promises. Don't take this the wrong way but I'm looking for some help if anyone has any ideas not requests or compliments on previous work (though both are appreciated)
Sent from my Galaxy Nexus using Tapatalk 2

Can you use windows xp to compile kernels?

helikido said:
Can you use windows xp to compile kernels?
Click to expand...
Click to collapse
no
10 char

No but ty for the try....looks like imma have to revert back to 11.10...so let it be known for best results on compiling android use Ubuntu 11. If u have Ubuntu 12 and it works fine then leave it and good for u
Sent from my Nexus S 4G using Tapatalk 2

Hey there! Try downgrading gcc and g++ to version 4.4. If that doesn't work you can always just set up a dev VM in xen or vmware instead of blowing away the whole box. Hope that helps.

[Kernel] Shield Portable Kernel Development [Incl. Guide]

Welcome to the first custom kernel for the KitKat Shield.​
This thread is for the development and building of the Shield Portable kernel.
This is not intended to download a build, post issues, and return when fixed.
Kernel Source:
https://github.com/StarKissed/starkissed-kernel-roth
Kernel Downloads:
https://goo.im/devs/playground/shieldroth
The kernel can be built using the commands below or the included script.
Code:
make tegra11_android_defconfig -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
make tegra114-roth.dtb -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
make -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
App & Donations:
StarKissed [SKU] on Google Play allows you to configure many of the options provided by this kernel. Issues or comments about the app can be posted at the XDA StarKissed app thread
Donations are not being collected through the forum. If you would like to donate, you may do so through StarKissed [SKU] on Google Play by using the donate options located in the top right (the green dollar bill guy).

[Kernel] Shield Kernel Development
The included ramdisk is for update 98. If you are on 72, this will most likely result in a bootloop. Using the 72 ramdisk will not work with this kernel, as the source is specific to "OTA 5" according to the Nvidia gitweb.

I recently updated the source and changed a few commands that may explain why current source resulted in non-working builds. I will be testing builds soon and then begin modifying the kernel once the core build is verified working.

Nice, I hope there will also be an overclocked kernel for 4.4. I know it's silly but I miss the 4.3 overclocked kernel.

rylen said:
Nice, I hope there will also be an overclocked kernel for 4.4. I know it's silly but I miss the 4.3 overclocked kernel.
Click to expand...
Click to collapse
All the code is there, it just loops. I'm not sure what's going on with it. The shield tablet version works.

Quick question. Any chance you could update the usb ethernet drivers in this? Specifically, I'm suffering from this bug on an ASIX 88772 on the official kernel, and it seems their driver is rather out of date. Thanks, and keep up the good work!

bakageta said:
Quick question. Any chance you could update the usb ethernet drivers in this? Specifically, I'm suffering from this bug on an ASIX 88772 on the official kernel, and it seems their driver is rather out of date. Thanks, and keep up the good work!
Click to expand...
Click to collapse
Won't do much good until it boots

True enough, just thought I'd bring it up since it's a fairly easy fix. In the meantime, I threw together a stock kernel with an updated driver to get by. I had one problem after another with the latest official driver, but the good folks at LKML had already put some work in on v4.1.0 several years ago. Using drivers/net/usb/asix.c and usbnet.c from the 3.4.106 source built without problems.

Beginning to think I may have to settle for building against the full source on this one. It boots fine when doing that, but not built alone. The shield tablet builds fine alone, so there's no explanation for it.

you are going to make a new build of your kernel? if you need help with the tests i can help.

YamazakiRobert said:
you are going to make a new build of your kernel? if you need help with the tests i can help.
Click to expand...
Click to collapse
Things are a bit crazy, but once I can get all of the changes fixed up and it'll build clean, I'm going to try to run it over night.

Slightly off-topic, but I'll ask you since you're the only other person I know building a shield kernel. I built nvidia's kernel, changing only the two drivers associated with my ethernet, but for some reason console mode has stopped working now. Have you ran into a similar problem? Plugging HDMI in pops up the selector, but clicking on console mode doesn't do anything - it just stays on the selector screen.

bakageta said:
Slightly off-topic, but I'll ask you since you're the only other person I know building a shield kernel. I built nvidia's kernel, changing only the two drivers associated with my ethernet, but for some reason console mode has stopped working now. Have you ran into a similar problem? Plugging HDMI in pops up the selector, but clicking on console mode doesn't do anything - it just stays on the selector screen.
Click to expand...
Click to collapse
It shouldn't be related. You may need to check the proprietary drivers. I believe HDMI is one.

Didn't bother to find out what the problem was, it just stuck around because I was doing dirty builds as I tested. Once I got a few other tweaks and had some time, I did a clean build and it resolved itself. Did you manage to get your kernel booting when building it by itself? I'm sure I'm doing something wrong there too, but I've been grudgingly building the entire device, since that at least works reliably.

What is so special about this kernel compared to stock ? goodjob already btw, you're one of the few who actually have a kernel
It's really sad how not much development is going on, it's such a good device there is only like 1 release at the original section :/