Database Develop

Rom cooking

so i am looking of getting into some rom and kernel cooking. haven't done it yet, but i am willing to give it a go. anybody have any tutorials on rom cooking? what do i need to set up to be able to create roms and save them etc.
any help will be appreciated. i am looking at starting to play with some HC for our beloved tablet.

I am going to stop dropping hints. Until we have all the drivers, a port will be useless. Ask all the devs over in the Vibrant Forums why theey still cann't get the GPS to work? Thye have had GB ported for a LONG time. But I'm not going to push this anymore. Now if Dell releases them, then we are in business, or if there is a possible way to extract the drivers from the stock img(s). Or if someone knows how to write the drivers for the hardware. And we will need a new kernel that is compatible with our device and hardware (that we do not have drivers for yet) because our stok kernel will only be compatible with froyo.
If you guys just wanna list reasons why I am wrong, don't waste your time typing them out. If i am wrong I will admit it if I am proven wrong. What I am hoping is that I am wrong, So prove me wrong PLEASE so we can get HC, if it is possible.

DJ_Steve who has worked with the streak 5 and has made other roms has said our kernel will work for gingerbread, it wouldnt work with HC without having to be recomplied but it should work with gingerbread. Also before you make the build you run a script called extract-files.sh (with your device connected via usb) and it will grab all the proprietary files and drivers that it needs from your working rom. and includes them in the build

i don't think i will get soo deep into cooking, but i will take my current rom and do a few mods to it, do a nandroid of it and post it here
i get home later tonight and i will try and work on something, but i won't promisse.

bogdi1988 said:
i don't think i will get soo deep into cooking, but i will take my current rom and do a few mods to it, do a nandroid of it and post it here
i get home later tonight and i will try and work on something, but i won't promisse.
Click to expand...
Click to collapse
Im ready to beta test them.

lou0611 said:
Im ready to beta test them.
Click to expand...
Click to collapse
i got home. will work on something for a couple of hours tops, but i won't promise anything.

ok. something with advanced launcher and a couple of extras will be coming soon.

ROM is up.

[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] Official PACman ROM Camera Problem

So I just installed the ROM and all is well, but the camera is not working at all. In the thread someone said that this is due to a driver issue with 4.2 ROMs. So simply my question is: Is this fixable or is this ROM just without a camera permanently? Of course if it is fixable, how would I go about doing that?

thatguywhoneedshelp said:
So I just installed the ROM and all is well, but the camera is not working at all. In the thread someone said that this is due to a driver issue with 4.2 ROMs. So simply my question is: Is this fixable or is this ROM just without a camera permanently? Of course if it is fixable, how would I go about doing that?
Click to expand...
Click to collapse
No it's not fixable. The reason is because it's based on Hash's work on the 3.0 kernel and while HD codecs theoretically work, we never did get the closed source camera drivers to build into that, so we don't have a way to get it to work. It's a pain in the butt and no one at Texas Instruments or Motorola wants to release something or throw a bone at us.

MrObvious said:
No it's not fixable. The reason is because it's based on Hash's work on the 3.0 kernel and while HD codecs theoretically work, we never did get the closed source camera drivers to build into that, so we don't have a way to get it to work. It's a pain in the butt and no one at Texas Instruments or Motorola wants to release something or throw a bone at us.
Click to expand...
Click to collapse
Ahh... Well Thanks anyways. lol

camera issue on PAC man rom
I just put this rom onto my phone three days ago. I flashed two other ROMs but ended up returning to this one. The first time I flashed it the camera did not work but the second time, for whatever reason, is working perfectly fine. Just thought I'd let ya know!

How is Cyanogenmod on the Tab S?

I have a Tab S. Great for watching videos. Awful for everything else.
I've been thinking of modding it with Cyanogenmod. And especially to get rid of those capacitive keys on the bezel, worst design decision ever on a tablet.
What is the status of CM on the Tab S? Is it noticably faster? Better? Worth the trouble?
I'm horrible at modding tablets. Last one took me like 4 hours. What is the best distro and method?

taiwwa said:
I have a Tab S. Great for watching videos. Awful for everything else.
I've been thinking of modding it with Cyanogenmod. And especially to get rid of those capacitive keys on the bezel, worst design decision ever on a tablet.
What is the status of CM on the Tab S? Is it noticably faster? Better? Worth the trouble?
I'm horrible at modding tablets. Last one took me like 4 hours. What is the best distro and method?
Click to expand...
Click to collapse
I can't speak on the how long it would take to install or anything like that, but based on the CM11 thread in the Galaxy Tab S General section, it seems like its flying and is working very well.

Development for CM is getting some progress, but I would wait till most things on it are almost bug free or at least when its stable is when I would install it. I believe you have to install the kernal and rom with twrp? Personally Im not going to install it since it deals with a custom kernal. Im fine with installing custom roms but installing custom kernals is what scares me since this is my first android tablet. As if now im on stock rooted rom (with debloated and frozen apps)and I get about 8 hours on just watching youtube.

Flashing a custom kernel is no different than flashing a custom ROM. You install a ZIP file through CWM or TWRP. The risks involved are the same. Flash the wrong file and your tablet is a shiny paperweight.

Ceep cool, guys. Flashing is no rocketscience.
Rule of thumb: as long, as you don't flash a recobery image, you always can go back to recobery (from where you can restore your nandroid) - even if you destroy your recoverypartition, you can go in donwloadmode and reflash a recovery from odin. Making a paperweight of your tab by flashing a costumrom (which inderd contains a non-sammy kernel) is quite unlikely.
So go ahead. Knox will be broken permanently - but there are quite a lot threads.
Nvertigo

nvertigo67 said:
Ceep cool, guys. Flashing is no rocketscience.
Rule of thumb: as long, as you don't flash a recobery image, you always can go back to recobery (from where you can restore your nandroid) - even if you destroy your recoverypartition, you can go in donwloadmode and reflash a recovery from odin. Making a paperweight of your tab by flashing a costumrom (which inderd contains a non-sammy kernel) is quite unlikely.
So go ahead. Knox will be broken permanently - but there are quite a lot threads.
Nvertigo
Click to expand...
Click to collapse
Thanks for that! But what would happen if odin cant flash stock back on. Like some people had some error in which they needed a pit file so odin can flash a rom on a device. How would you get a pit file?

DUHAsianSKILLZ said:
Thanks for that! But what would happen if odin cant flash stock back on. Like some people had some error in which they needed a pit file so odin can flash a rom on a device. How would you get a pit file?
Click to expand...
Click to collapse
You are right. "quite unlikely" implies it's still possibble the some people can do something and some devices have afterwards some errors... For sure: you van brick and even hard brick devices - but it's unlikely, if you do your homework (reading, reading and reading... ). If you don't feel comfortable after research, stay away from flashing. 'Cause - again: youmare right - it is possinle to hard brick an expensive device.

nvertigo67 said:
You are right. "quite unlikely" implies it's still possibble the some people can do something and some devices have afterwards some errors... For sure: you van brick and even hard brick devices - but it's unlikely, if you do your homework (reading, reading and reading... ). If you don't feel comfortable after research, stay away from flashing. 'Cause - again: youmare right - it is possinle to hard brick an expensive device.
Click to expand...
Click to collapse
Im fine with flashing with twrp. Its just odin is what i stay away from. I still have my stock rooted rom backup in twrp. Its just the backup has a messed up hosts file in which google servers are blocked. So everytime i restore to my backup i have to download root broswer from the internet browser and delete the hosts file.

Waitin for multirom to be non stocknkernel usable..then illl test cm11

Ok but what about performance CM11 vs stock? CM11 is better? I hate LagWiz.. it's incredibly irritating especially i have LG G2 withCM11 that works fine and really smooth. I'm afraid of knox flag but I'm ready to risk if CM11 change my Tab S and let me forget about lags.

robson2222 said:
Ok but what about performance CM11 vs stock? CM11 is better? I hate LagWiz.. it's incredibly irritating especially i have LG G2 withCM11 that works fine and really smooth. I'm afraid of knox flag but I'm ready to risk if CM11 change my Tab S and let me forget about lags.
Click to expand...
Click to collapse
I only LagWiz is anoying install Novalauncher or any other third party launcher and delete sammy Launcher with Titanium.
If you want the fullcm-expirience: go for cm. It's development, mic broken, and some other issues (hey, there is a thread where progress on this cm is discussed), but its quit stable and fast. And its true cm.

I only LagWiz is anoying install Novalauncher or any other third party launcher and delete sammy Launcher with Titanium.
Click to expand...
Click to collapse
I have Nova but i need root to delete TW launcher?
I will follow cm's thread. Thanks

robson2222 said:
I have Nova but i need root to delete TW launcher?
I will follow cm's thread. Thanks
Click to expand...
Click to collapse
Whatever the android related question might be - the answer is nearly always: first you need your device rooted...
Yes you need root for uninstalling system apps.
For cm you need a costum recovery, and cm comes rooted.

nvertigo67 said:
I only LagWiz is anoying install Novalauncher or any other third party launcher and delete sammy Launcher with Titanium.
If you want the fullcm-expirience: go for cm. It's development, mic broken, and some other issues (hey, there is a thread where progress on this cm is discussed), but its quit stable and fast. And its true cm.
Click to expand...
Click to collapse
As far as I know the mic is working just fine.

eousphoros said:
As far as I know the mic is working just fine.
Click to expand...
Click to collapse
Probably on klimtwifi and chagallwifi - but not on chagallwifi. Thats one of the main issues. The sound implementatikn seems to differ on all the 5420 devices.
BTW: Thanx for your work on kimt wifi. From my point of view it lools like crpalmer (cm picassowifi maintainer) started from your work, and I started from picassowifi... So: Thanx.

I had to rewrite a chunk of the audio primary hal and created a mixer_paths.XML from scratch. It even involved some printk love in the kernel to figure out what the kernel driver was expecting. Probably some of the toughtest (though all entertaining) part of the port for me.
If you have questions I might be able to help.

eousphoros said:
I had to rewrite a chunk of the audio primary hal and created a mixer_paths.XML from scratch. It even involved some printk love in the kernel to figure out what the kernel driver was expecting. Probably some of the toughtest (though all entertaining) part of the port for me.
If you have questions I might be able to help.
Click to expand...
Click to collapse
I come back to your offer. Few days ago I wrote: mixer_paths.xml was invented by a much more complex mind then me... Now I get to now him... At the moment a had tomslow down a little and get some distance, but I would be glad to contact you in a few days. Thank you.

nvertigo67 said:
I come back to your offer. Few days ago I wrote: mixer_paths.xml was invented by a much more complex mind then me... Now I get to now him... At the moment a had tomslow down a little and get some distance, but I would be glad to contact you in a few days. Thank you.
Click to expand...
Click to collapse
I totally understand the distance thing. I got lost in getting the initial port up. Probably took me close to 80 hours over the period of three weeks. I now restrict myself to checking the forums twice a week and one night a week coding on the port.

eousphoros said:
I totally understand the distance thing. I got lost in getting the initial port up. Probably took me close to 80 hours over the period of three weeks. I now restrict myself to checking the forums twice a week and one night a week coding on the port.
Click to expand...
Click to collapse
It will be really great to see a cm port for the 8.4inch lte model as well.your port for the wifi was really popular.
Honestly,tab s has one of the better hardware out in the marke.but TW is quite another matter.
i dun see any cm in the forums to make me wanna trip that knox crap. and i am holding out for the xperia z3 compact tablet.the pces on that on is comparable with the tab with only the screen losing out.

I find it quite astonishing to read so often about the horrible experiences with the tab s. Maybe im living in a parallel universe, as i love the tab s, and i havent even debloated it yet.
Sure there are micro stutters, but much less then on my iPad 4. The screen is great and everything else is working flawlessly for me... even the apps are nearly on par with iOS. I wont go back,
thats for sure... just wonder whats up with all those complains.

[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 :/