Database Users

Kernel build on Dev Phone 2 (Sapphire)

Hi All,
I have a Dev Phone 2 with a 32B board.
I have downloaded the Sapphire source tree from HTC, and I have attempted to compile it (I am familiar with kernel build/hacking, though not on this platform...yet) The kernel, as it is configured "out-of-the-box" does not compile. It seems to die trying to build the touchscreen driver, among other things.
This is consistent with other posts i have seen about part of the kernel being "proprietary"
I am trying to understand two things:
1. Is it possible to rebuild this kernel? Or is the kernel source only provided so that I can build modules aganst it.
2. If so, how do I get around the build problems i am seeing?
Many thanks!

i would post in the sapphire dev forum, or also the g1 dev forum, as the dev's who visit those may be able to help you with your compiling issues...
good luck...
also check www.theunlockr.com as they have build guides for most devices (i know they have 32B guides)

(READ BEFORE TRYING)Some answers to questions

Ok people a slight helpful guide here, may have already been created but its here regardless
This will also be posted in Q&A under answers just to help people out
So in the Q&A forum i have seen a lot of the same question, my X10 is stuck at boot, which yeah happens but it seems to be for the same reason due to kernel or mod damage so what can you do?
i will also answer from experience on other questions
No1. READ the requirements...
These are the requirements for the ROM i use (DiXperia7 Avenger from DikeJ), (They generally follow same lines but dont suspect they do.)
OS - Android 2.3 or 2.1 (from upgrade from 2.1 to 2.3 wipe will be needed)
Permissions - Root Access, Busy Box, Xrecovery (Kernels for Stock roms not CM series)
Optional - Unlocked bootloader running DoomKernel v6 or above. Seeing as this seems to be final edition from the great doomlord we shal settle there.
So as you can see some simple requirements laid out nicely, bootloops and boot freezes can normally relate to Kernels installed, if theres a problem it wont install or freeze anyways but normally a ROM freeze is picked up before its released.
On locked bootloaders you wont have this problem as long as the ROM supports this. The dev will normally tell you what you need if not ask.
No2. ASK!
of course i am trying to help less skilled people, like me, avoid bootloops and crashes. so always as on the dev forum and wait for a reply, chances are its been tested but if your unsure dont do it until you know 100% and a dev or someone with experience has tested personally.
No3. Make sure your using the correct recovery.
It works like this.
Stock ROM - Xrecovery (DoomKernel ThKernel)
Cyanogenmod series - Clockwork Recovery mod (In FXP Kernels)
MIUI Series - Can be both but seems mainly Clockwork
championswimmer has done a custom version of both CWM and Stock - http://forum.xda-developers.com/showthread.php?t=1564056 credits go to champ.
So enough about Kernels and blah blah xD lets move onto Wifi Troubles
Wifi runs using the Kernel, Unlocked bootloaders need a patch to run Wifi unless its FXP based.
These files are generally found with the kernel on the forums. Known as wifi modules.
You can flash these patches before 1st boot but its not recommended. needs to be reinstalled every time you flash a rom as there wiped out..
(Please make sure the wifi patch is correct to the kernel as a wrong one will not fix wifi errors)
Random Reboots while phone is on.
Ok i dont know highly on this subject but i do remember reading a little about them..
Random reboots can be caused due to hardware failure, normally motherboard crashes, just restart the phone by removing battery normally works.
Another factor of this is a mod that has been installed. If the mod is not designed for your phone it will normally cause a bootloop at kernel but if it gets pasted this could be a cause of your problems.
SuperUser detection not working :S?
I had this problem, SU was stopping my root programs getting there access, but sometimes the app isnt at fault, its your actual root, simply rerooting fixes this .
Ok people i hope this helps just to help new users out on problems, although as always i wont be held responsible for any damages.
Thanks to..
DoomLord - DoomKernel Series
Champ - Kcernal series
ThJap - ThKernel Series
FXP - for the CMW recovery and there kernels
The Devs who fix, create and keep the X10 going
The Q&A forum for asking and answering questions all day long

XDroidie626 said:
Ok people a slight helpful guide here, may have already been created but its here regardless
This will also be posted in Q&A under answers just to help people out
So in the Q&A forum i have seen a lot of the same question, my X10 is stuck at boot, which yeah happens but it seems to be for the same reason due to kernel or mod damage so what can you do?
i will also answer from experience on other questions
No1. READ the requirements...
These are the requirements for the ROM i use (DiXperia7 Avenger from DikeJ), (They generally follow same lines but dont suspect they do.)
OS - Android 2.3 or 2.1 (from upgrade from 2.1 to 2.3 wipe will be needed)
Permissions - Root Access, Busy Box, Xrecovery (Kernels for Stock roms not CM series)
Optional - Unlocked bootloader running DoomKernel v6 or above. Seeing as this seems to be final edition from the great doomlord we shal settle there.
So as you can see some simple requirements laid out nicely, bootloops and boot freezes can normally relate to Kernels installed, if theres a problem it wont install or freeze anyways but normally a ROM freeze is picked up before its released.
On locked bootloaders you wont have this problem as long as the ROM supports this. The dev will normally tell you what you need if not ask.
No2. ASK!
of course i am trying to help less skilled people, like me, avoid bootloops and crashes. so always as on the dev forum and wait for a reply, chances are its been tested but if your unsure dont do it until you know 100% and a dev or someone with experience has tested personally.
No3. Make sure your using the correct recovery.
It works like this.
Stock ROM - Xrecovery (DoomKernel ThKernel)
Cyanogenmod series - Clockwork Recovery mod (In FXP Kernels)
MIUI Series - Can be both but seems mainly Clockwork
championswimmer has done a custom version of both CWM and Stock - http://forum.xda-developers.com/showthread.php?t=1564056 credits go to champ.
So enough about Kernels and blah blah xD lets move onto Wifi Troubles
Wifi runs using the Kernel, Unlocked bootloaders need a patch to run Wifi unless its FXP based.
These files are generally found with the kernel on the forums. Known as wifi modules.
You can flash these patches before 1st boot but its not recommended. needs to be reinstalled every time you flash a rom as there wiped out..
(Please make sure the wifi patch is correct to the kernel as a wrong one will not fix wifi errors)
Random Reboots while phone is on.
Ok i dont know highly on this subject but i do remember reading a little about them..
Random reboots can be caused due to hardware failure, normally motherboard crashes, just restart the phone by removing battery normally works.
Another factor of this is a mod that has been installed. If the mod is not designed for your phone it will normally cause a bootloop at kernel but if it gets pasted this could be a cause of your problems.
SuperUser detection not working :S?
I had this problem, SU was stopping my root programs getting there access, but sometimes the app isnt at fault, its your actual root, simply rerooting fixes this .
Ok people i hope this helps just to help new users out on problems, although as always i wont be held responsible for any damages.
Thanks to..
DoomLord - DoomKernel Series
Champ - Kcernal series
ThJap - ThKernel Series
FXP - for the CMW recovery and there kernels
The Devs who fix, create and keep the X10 going
The Q&A forum for asking and answering questions all day long
Click to expand...
Click to collapse
Nice post!

N4 Development/N4 Original Development - what's the difference?

Someone kindly explain what the difference is between the two forums? I can't figure it out. This
[Nexus⁴]

Same as other forums...it's meant to be
Development - stuff based on the stock image
Original Development - Stuff made from AOSP/scratch

yea me either.
in the N7 forums.. the Kernels I like which are MOTLEY are posted in the Android Development forum yet in the N4 forums... the motley Kernel is posted in the Original development section.
no consistency or description.
i would have to guess that Original development is for development not headed down the path of AOSP or Android aka Linux/Ubuntu etc.. and then android development is for AOSP Android directly related stuff?
Edit i was wrong its reversed from what I thought.

[samsung i857(doubletime)]ROM devlopers and users of this phone

HI all , i lunched this thread after weeks of googling and usless search for a new stock or custom rom to update my phone (samsung sgh-i857 doubletime) it's a dual screen phone with querty built-in keyboard it's from at&t and it is stuck on android 2.2.2, i'm very sad that they and after years from lunching it didn't back it up with a single soft update -_- ... and i know that there are users who bought this phone like me and seek help.. i know that it's not this easy but if you are a devloper help us by creating a custom rom for it ....if you are a user of this phone please support this thread by commenting so we can get an update for it :good: ps: i attached informations for it's cpu

Hello good sir, I like you am a noobish Doubletime user who is struggling to update it to Gingerbread. So far I have been somewhat able to use the Cyanogenmod source code and I have built a CWM Recovery for the device but that seems to have hard bricked it... I ordered a new one off ebay for $15 and I'm ready to start cooking. You have my support!

Just an update.
I have a plan I have on how to get this runnin.
1. Port CWM to the DoubleTime through Cyanogemod 6.
2. Get a working version of Cyanogenmod 6 working on the DoubleTime to hopefully free up some space.
3. Find if Gingerbread can run on Froyos kernel.
From there I'll either be building a GingerBread compatable kernel or Cyanogenmod 7 depending on compatability. Any advice or help would be very appreciated.

Being new to ROM building I'm a little lost and hesitant on flashing things but here's what I know so far.
The DoubleTime uses a Qualcomm MSM7230 same as the HTC Vision. I forked it's Github respiratory and I'll be using it as a base as recommended by the Cyanogenmod porting guide.
The partitions sizes (as a accurately as I can estimate them) are:
/cache=21.05MB
/data=176.65MB
/system=194.38MB
I may need to know the recovery partition size but I'm not sure how to find that out.
I have the recovery.img and the boot.img as well as the zImage. So as soon as the repo sync is done I'll be on my way.

I'm back again today with somewhat mixed news, I can find most of the partitions and their names (I've learned a lot today) but I can not seem to find the boot, recovery or ramdisk partitions. I'm already boggled by the what seems to be unconventional naming setup for partitions. Put all of my "notes" in a text docement in the attachments section. Any help with this is very appertiated. I can type and post anything into the ADB shell you need me too.
I'm beginning to feel like I'm talking to myself, I probably am...

Upon reading forum rules and such it has come to my attension that this is the wrong forum for this kind of thread, So I have made a new thread in the Miscellaneous Android Developement Forum that will hopefully be more useful at getting more proffesional and opinionated help.
http://forum.xda-developers.com/showthread.php?t=2651728

REQ rooted kernel 5.1.1 for Sm-t235 (source was published a month or two back)

sometime back this was posted
http://forum.xda-developers.com/showpost.php?p=63556533&postcount=135
unfortunately moonbutt closed his thread just when I and another member posted boot image etc on the board..understand he may have moved on to better things
not knowledgeable here but appreciate if someone can take this up or redirect this to some dev who can make a rooted kernel since the source has been published
thanks

SM-T237P
Would love to root my 5.1.1 tab , so I too would be begging for another developer to step in to fill this need. I need a kernel with UVC video support.

OKAY so now I know my posts were getting deleted when I asked for T235 kernel root
zitomd said:
Would love to root my 5.1.1 tab , so I too would be begging for another developer to step in to fill this need. I need a kernel with UVC video support.
Click to expand...
Click to collapse
yesterday or may have been on Sat night, on the T533 thread I tried to catch moonbutt's attention by pointing to the T235 source (when apparently he was saying the T533 had no source but was addressing that kernel) and now that post has gone like on his closed thread (just when it seemed he was taking an interest thanking me for providing boot.img and other files)
anyway...need some dev who can volunteer to work on this and at least someone who would respond yes or no (deleting posts maybe to avoid a side conversation)
I pulled the source started to look it up and looked up on how to modify kernel..looked doable to a point but this is from a total novice (all i know is to mod some apk, compile/re-compile but no building stuff)

mac231us said:
yesterday or may have been on Sat night, on the T533 thread I tried to catch moonbutt's attention by pointing to the T235 source (when apparently he was saying the T533 had no source but was addressing that kernel) and now that post has gone like on his closed thread (just when it seemed he was taking an interest thanking me for providing boot.img and other files)
anyway...need some dev who can volunteer to work on this and at least someone who would respond yes or no (deleting posts maybe to avoid a side conversation)
I pulled the source started to look it up and looked up on how to modify kernel..looked doable to a point but this is from a total novice (all i know is to mod some apk, compile/re-compile but no building stuff)
Click to expand...
Click to collapse
mac,
i had your post removed because it was interfering in H's thread. I tried with this device a little while ago but testers seem to think they are at liberty to not follow instruction, or just change their minds mid-stream like they haven't just wasted my time and resources. . The upside would be if you have the source and the setup to compile it and thereby test your own work then, i can absolutely run you through what you need to do, The tricky part is knowing which tools you need for the packing/unpacking of the ramdisk.
If this is a qcom/msm device you will need AIK which is the best solution.
If this is a marvell variant you will need ketut's degas bootimg toolkit which is the best solution.
You need [likely] to apply the patch mentioned in my thread to security/selinux/selinuxfs.c
Be aware that samsung's source releases are usually incredibly sloppy and the defconfigs for devices are usually somewhat off, missing config settings.
Check for sdcardfs xattrs, virtual xattrs, etc . you need to make sure those are selected in order for your internal and external storage to mount.
Find the correct defconfig for your device and post it as a zipped attachment. or check my thread and look at my sources on git, specifically the commit history [msm devices mostly] to get an idea of what you need. You can get a linux os running in a virtual machine and compile just fine as long as you have all the pre-requisites installed. The getting started link in my signature is a rough/general guide to help get you up and running.
m
ps, my thread is just locked, not closed, i was getting too many OT/non-dev postings. I open it when/if i have something new and then close it again.

thanks moonbutt74...totally understand...appreciate the links in your signature and other resources...will start looking into it (long long journey but gotta try)

mac231us said:
thanks moonbutt74...totally understand...appreciate the links in your signature and other resources...will start looking into it (long long journey but gotta try)
Click to expand...
Click to collapse
mac,
no prob, recommended step 1, get your linux distro set up, stongly recoommend kali/debian 2.0, either in vm or better as 2nd os in a dual boot scenario.
m