[REQ] Need some logs from NS for SGSport - Nexus S Q&A, Help & Troubleshooting

Hey Guys.
I need some logs from Nexus S for our SGSport project.
Someone with a Nexus S has to build a kernel with following options enabled:
CONFIG_FB_S3C_DEBUG=y
CONFIG_VIDEO_FIMC_DEBUG=y
CONFIG_VIDEO_MFC50_DEBUG=y
CONFIG_VIDEO_JPEG_DEBUG=y
After flashing open Youtube and watch a video.
While watching the Video:
adb shell
dmesg
^^ copy the whole output to http://www.pastebin.com
logcat
^^ copy the whole output to http://www.pastebin.com
Would be very nice if someone can do it.
Same for Camera please.
Thank u guys.

Pl0x nexus S people??
Sent from my GT-I9000 using XDA App

I can compile a stock kernel with these options selected later and post it up if someone wants to flash it and get the info.
Sent from my Nexus S using XDA App

Here's a stock kernel with the debug options selected as requested above. I'm not running a stock rom or I'd flash it and grab the results (stock rom breaks the CM camera if I recall correctly). Anyone who wants to grab the data just nandroid, flash the kernel, push the wifi module and go to town.

can anyone post exactly which battery model or battery driver is used for the nexus s? can either look in the config file when compiling your own source ROM. or perhaps find the battery driver folder using root explorer etc.
just curious to see if similar changes could be made like we did with the nexus one battery driver (the app link in my sig).

Related

[DEV-ROM] HTC Evo Full AOSP rom Android 2.2.1|FRG83

I'm posting a developmental rom for the purpose of anyone and everyone that want's to cook an AOSP rom but is having troubles or doesn't want to go through the hassle of compiling from source. This Rom is completely compiled from AOSP source with the help of the CM team for the HTC Device tree and kernel.
There are many non-working item's. For anyone that uses this rom and tries to fix the issues, if you could please post on this forum for everyone else to do the fixes that would be awesome. I've included the link to the Rom and a link to the Google Apps flashable zip from CM's Wiki.
Click to expand...
Click to collapse
Once again this rom is a Dev-Rom and is completely compiled from AOSP source, this has no sense at all and will never have sense. I will not be maintaining the rom per se, I will however be helping with some of the fixes.
Evo Android 2.2.1 AOSP ROM
Google Apps
Thanks to: Bcnice20, l33tlinuxh4x0r, tjohnsonjr & the CM team.
These are insturctions for making a clean AOSP Rom. There will be issues with the Rom once you finish. These instructions are for Linux(I used Ubuntu). You will have to have adb installed already. Your computer has to be 64bit or you not be able to compile the source.
Please Note. 4G and HDMI will not work. This is not a stripped down Sense Rom. There is no SENSE AT ALL!!! The Camera will work but not the Camcorder. Fixes will come but we are hoping to get contributions from other devs to help build up the AOSP support for the EVO. As great as CM6 is, we need choices. Now let the fun begin!!!
Open the Terminal:
The following needs to be ran as Root
Code:
cd /usr/bin/
curl http://android.git.kernel.org/repo > repo
chmod a+x /usr/bin/repo
Exit root and return back to your home folder. This will create a generic build. This is going to take a couple of hours depending on your internet connection
Code:
mkdir ~/android
cd ~/andoid
repo init -u git://android.git.kernel.org/platform/manifest.git
repo sync
This will download the EVO specific files:
Code:
cd ~/android/device/htc
git clone http://github.com/CyanogenMod/android_device_htc_supersonic.git supersonic
Now the BoardConfig.mk needs to edited
Go to /android/device/htc/supersonic/BoardConfig.mk
Locate
Code:
TARGET_RECOVERY_UI_LIB := librecovery_ui_supersonic librecovery_ui_htc
TARGET_RECOVERY_UPDATER_LIBS += librecovery_updater_htc
Now add a “#” in front of each line
Code:
#TARGET_RECOVERY_UI_LIB := librecovery_ui_supersonic librecovery_ui_htc
#TARGET_RECOVERY_UPDATER_LIBS += librecovery_updater_htc
Save and exit. Then in the terminal type
Code:
cd ~/android
cp ~/android/device/htc/supersonic/supersonic.mk ./buildspec.mk
Now Go to /android/frameworks/base/core/res/res/values and locate the Config.xml file. Open with the text editor and look for this line
Code:
<string name="default_wallpaper_component">@null</string>
Right below this line add. Reference this website to use as an example as to what its supposed to look like http://pastebin.com/mpmpEaKq
Code:
<!-- Handle notifications differently if device only uses an amber/green
LED. This also needs a liblights module that enables them accordingly. -->
<bool name="config_amber_green_light">true</bool>
Save and exit
Now load Cyanogenmod6 onto your phone. Once its loaded, connect your phone to the computer and in the terminal type
Code:
cd /device/htc/supersonic
chmod a+x extract-files.sh
./extract-files.sh
This will download files from the phone. You will get errors at the end. Get a stock Sense Rom and locate the files that came up in error and Copy the files into /android/vendor/htc/supersonic/propietary folder
Now in the Terminal
Code:
cd ~/android
. build/envsetup
lunch
Select option for the supersonic(6th or 7th)
Now type(This will take awile depending on the speed of your computer)
Code:
make
Once it finishes, type
Code:
make otapackage
Lastly, to get the phone to boot, get the libmedia.so file from CM6 and place it in your /system/lib folder before flashing.
This will create your ROM is a zip file. DO NOT FLASH THIS TO YOUR PHONE. IT IS NOT ROOTED AND IF YOU FLASH IT WITHOUT ADDING ROOT PERMISSIONS, YOU WILL LOSE ROOT. YOU HAVE BEEN WARNED.
ENJOY
Might as well grab me a spot n case I come across nething
I like this idea. So this is AOSP compiled for the EVO with no changes at all?
Nice work buddy
illogic6 said:
I like this idea. So this is AOSP compiled for the EVO with no changes at all?
Click to expand...
Click to collapse
Yes. This is completely stock with no modifications
Im no dev but I'd like to learn... would this be a good Rom to start with?
Sent from my PC36100 using XDA App
This looks very promising, AOSP choices are a limited in the evo department
I've seen the aosp rom in the heroc forum, that thing is a beast even compared to cm. So much potential on the evo, thank you so much!
Sent from my PC36100 using XDA App
overthinkingme said:
I've seen the aosp rom in the heroc forum, that thing is a beast even compared to cm. So much potential on the evo, thank you so much!
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Can you post the link for this?
Sent from my PC36100 using XDA App
Nevermind I read OP again.
jm5503 said:
Can you post the link for this?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
See my signature
Sent from my HERO200 using XDA App
I assume no 4g?
Am I the only one who can't get titanium backup to work??
Sent from my PC36100 using XDA App
jm5503 said:
Am I the only one who can't get titanium backup to work??
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I believe titanium backup requires Busybox and that rom base does not have it installed. You should be able to install the busybox installer from the market.
wrod7 said:
I assume no 4g?
Click to expand...
Click to collapse
no 4g, no hdmi
I'm having a hard time getting busybox installed and superuser permissions working properly....can someone help me or upload a version with these working?
Sent from my PC36100 using XDA App
jm5503 said:
I'm having a hard time getting busybox installed and superuser permissions working properly....can someone help me or upload a version with these working?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Same Thing Here
Surprised we haven't seen this before.
I thought about trying to strip CM down to AOSP basics, since I've been too lazy to get something running from scratch.
I'm looking forward to messing around with it. At work right now and can't grab it yet, have most/all of the CM Evo specific fixes been added, like notification LED support (I assume the AOSP tree is made for the N1) and camera support?
Kinda separate question, but what is the difference (if any) in the official Nexus One builds that get pushed out to the phones OTA and doing a build from AOSP and flashing the Google Apps?
does hdmi and or 4g work with this

[ROM][27 APR] Puregandroid v 1.1

PUREGANDROID
About
PUREGANDROID ( Pure Google Android) is a pure android os as google intended.
It uses a CM7 base but most if not all CM7 is removed. This is my first rom and I could not remove all CM7 but I will remove more in the Future (cyanogenmod in setting ( Please I need some help on this) and the RenderFX widget( can't locate it)
UPDATE:
I have posted a beta to see if you guys like it it was built from CM and AOSP sources. I just have to compile kernel and change lockscreen.
NEW WEBSITE
macaddict.tk
DOWNLOAD
http://dl.dropbox.com/u/27168952/DOWNLOADS/PURG3.oBETA.zip
HOW TO FLASH
*USE CWR
1. wipe all user data
2. wipe cache
3. install from SDCARD
4. Select rom
5 reboot
About:
Uses Google stock launcher
Includes all google apps
Has North America GPS FIX
Uses a CM7 Kernel (for it to be stable)
Wants in Future
Ablsolutly no CM7
pure google
overclock to 1.5 or 1.8
Changes in 2.2
New aosp settings menu and more cygen removed
Lockscreen still needs editing
NOTICE
I TAKE NO RESPONSIBILITY FOR LOSS OF DATA OR AND DAMAGES.
I'm confused.
How can it be based on CM7 yet have all the CM7 removed ?
Sent using XDA Premium running MIUI version in OP
symonc said:
I'm confused.
How can it be based on CM7 yet have all the CM7 removed ?
Sent using XDA Premium running MIUI version in OP
Click to expand...
Click to collapse
I was thinking the same thing.
OP You should start with aosp source and fix that if you want as pure as google android as you can get.
By the way you your picture you have up there is not stock launcher it's adw launcher. And the rotary lock screen is not stock either. Sorry.
Sent from my Incredible using Tapatalk
I have the stock launcher installed in this version that screenshot is old. The Google lockscreen is included but not set as default ( trying to learn how to do this). I have remove Most of the CM stuff except for somethings i need to learn ( edit settings.apk to remove The CM settings ( which will not open when clicked on). All the apps on this rom come from a aosp rom for the DroidX( except for Terminal, Rom Manager, and File Explorer (which is very useful). All traces that i can remove so far have been removed.
haha dicks, just rippin him apart and the rom hasnt even been out for a day LOL
I applaud the effort. Congrats on your first rom and look forward to see the improvement. As far as removing apps, one thing I do is find it in Titanium then see what the file is named, then you can remove it out of the app folder.
Like stated above, you should work with a pure aosp base and you won't have to worry about any of that CM7 stuff. In my opinion, I think aosp is about as smooth as it gets when it comes to UI. I'm sure people would love to have a pure aosp ROM around here since there aren't any yet that I'm aware of.
Good luck with everything and if you need any help just ask.
I'll give a shot. I love loading new roms. Thanks and good luck.
The problem is that I remove CMparts.apk and cyanogenMod settings is still in my settings menu (like a ghost menu ( it won't open). I need someway to edit setting.apk to remove this from the settings menu but im not skilled enough to do this any help would be apreciated.
Also The RenderFX widget is unable to be found (If someone has a location or what file it is in please tell me)
tell me how it is please!!!!!
OP There is a lot more to removing cm then you are thinking. Cm is not just the addition off apps but also modification of all what is android. If you want aosp start with aosp
Sent from my Incredible using Tapatalk
Ok I tried it and honestly it looks just like cm7. I don't know about creating roms but it seems that this is cm7 renamed and the boot screen changed. I would seek advice on properly creating roms and start over. Good luck.
cpbeats said:
Ok I tried it and honestly it looks just like cm7. I don't know about creating roms but it seems that this is cm7 renamed and the boot screen changed. I would seek advice on properly creating roms and start over. Good luck.
Click to expand...
Click to collapse
It's because it is. I will gladly offer my help to the OP. Hit me up if you like OP @linuxmotion or pm.
Sent from my Incredible using Tapatalk
If I were to create this from a aosp rom I first need to get my hand on one. I need to get drivers (I have no Idea on how to do drivers). And what kernel would I use. also what drivers would i need and don't need (screen, mix, speaker, touchscreen, bluetooth,wifi?)
Also would you want to make this rom with me?
nerdkiller14 said:
If I were to create this from a aosp rom I first need to get my hand on one. I need to get drivers (I have no Idea on how to do drivers). And what kernel would I use. also what drivers would i need and don't need (screen, mix, speaker, touchscreen, bluetooth,wifi?)
Also would you want to make this rom with me?
Click to expand...
Click to collapse
You might want to check with @DOAlaboratories. He was working on an AOSP ROM, but hasn't updated his thread in a while.
http://forum.xda-developers.com/showthread.php?t=999988
nerdkiller14 said:
If I were to create this from a aosp rom I first need to get my hand on one. I need to get drivers (I have no Idea on how to do drivers). And what kernel would I use. also what drivers would i need and don't need (screen, mix, speaker, touchscreen, bluetooth,wifi?)
Also would you want to make this rom with me?
Click to expand...
Click to collapse
Building from source ie. google. You can google ginger bread aosp and it will bring up this or from Git. You are going to have to build a kernel from source as well. You take the drivers that inspire already has. Its alot of trial and error to see what works and what doesn't.
Is there anywhere that has all the information necessary to build a rom compiled into one handy area?
Sent from my HTC Desire HD using XDA App
Google is your friend if you want to learn how to compile asop. You can check out the android source site http://source.android.com/ or the developer sitehttp://developer.android.com/
Sent from my Incredible using Tapatalk
I have found a outdated 2.3.1 Asop rom for Desire HD (camera not working and USB mass storage not working ). Also If any one has any idea of how to copy CM7's drivers for USB and CAMERA I would love to hear from you!!!
Also How can I update this rom to 2.3.3 without having to recompile from ANDROID-SDK
I'm gonna take a crack at building from AOSP tonight. Gonna use the kernel and proprietary files from CM7. If it doesn't boot though, I don't have the patience to start looking into the kernel and framework to fix it. Wish me luck!

[Q] Building custom ROM could use a couple pointers...

Like the title says I'm working on building a ROM of my own. I am new to this but am not stupid. I've looked around the forums and have bookmarked quite a few threads that will help me. My question is, how would I go about putting a custom CWM flashing screen in? Like on Eman..and ZTR where it says Collective, and flashing modem, etc. etc. And if anyone can point me to a better "ROMS for dummies thread that would be great Thanks for any help
Edit: Scratch that question, just found it lol. But any pointers will still be appreciated
So you are set?
Sent from an Emancipated Infuse bleeding Orange
Are you on linux? If you are, then i sugest installing android utility, its probably the simplest way of getting everything installed and organize it all together. It installs dsixda rom kitchen, apktool, simpla adb interface-im out of town at the moment but when i get back (friday night) i can upload some pics of the android utility
http://forum.xda-developers.com/showthread.php?t=1167623
Sent from my SAMSUNG-SGH-I997 using XDA
^ Alright man thanks. I'll have to install a linux partition on my HDD but that's easy enough. I do have one question that's confusing me...How do I add things to my rom? For example the camera mod where you can take pics with the power button? I have the apk but when I replace it at system/app it Fc's. Do I need to put the other files that come with it in my rom? Same problem with EPM. I have the settings apk but it doesn't work..
FauxAffliction said:
^ Alright man thanks. I'll have to install a linux partition on my HDD but that's easy enough. I do have one question that's confusing me...How do I add things to my rom? For example the camera mod where you can take pics with the power button? I have the apk but when I replace it at system/app it Fc's. Do I need to put the other files that come with it in my rom? Same problem with EPM. I have the settings apk but it doesn't work..
Click to expand...
Click to collapse
For camera I believe you will also need to pull the camera firmware apk too-so you need to put the modded camera.apk and camera firmware.apk in your from (both can be obtained from any of bigfaus roms
For epm you need more than just the settings apk, you also need to replace the frameworks that come with epm (policy.jar, framework-res.apk, and framework-res.jar) I believe that's all you need
As always, if you choose to upload your rom for others be sure to give credit-bigfau for camera, and I'm assuming you got epm from dman so dman for epm
Sent from my SGH-I997 using XDA
Also for battery mods (and other stuff too) a great place to go is a website called UOT kitchen-just choose your battery mod then upload your frameworks and it will place the modded battery in there for you, then replace your old frameworks with the new ones from uot kitchen
*do this after you have epm set up and running...unless you plan on doing it manually using dmans how to guide*
Sent from my SGH-I997 using XDA

YouTube and root problem with aosp build.

OK,
So I made an aosp build from source for my nexus 7 2013 , but every time I go in youtube and click on a video to watch it the tablet make a hot reboot.
I tried watching a video that I downloaded from the internet within the gallery app(the aosp one) and no problem the video display fine.
Before I built the ROM I extracted the nexus binaries properly i don't know what's wrong.
Also I can't root my tablet with this build every time I flash supersu in recovery it fails.
Another thing, how can I root the ROM before building it, I mean , implementing supersu and busybox inside the ROM before the build process?
Thanks in advance.
Sent from my AOSP on Flo using XDA Free mobile app
Please someone.
Sent from my Nexus 4 using XDA Free mobile app

[CM12][Q/A] Discussion thread for CM12

This thread is for any questions regarding the CM12 build I'm making.
Link to ROM thread: Coming soon.
Sent from my GT-I9003 using XDA Free mobile app
Waiting for the rom
Excited to test it.
Still building..... Keeping my fingers crossed
Sent from my GT-I9003 using XDA Free mobile app
God I'm *this* close to success and it just won't get to the boot animation. *sigh*
Sent from my GT-I9003 using XDA Free mobile app
Has there been any progress on this ROM?
Why is porting so hard
As far as I understood, to get a new Android on Device X is as following: :silly:
1) Download latest CM-ROM
2) Copy drivers from Device X´s stock ROM to latest CM-ROM
3) Configure build.prop eg. screen resolution/DPI&co.
4) Zip and flash it
Am I right? Wrong? :cyclops::fingers-crossed:
[email protected] said:
As far as I understood, to get a new Android on Device X is as following: :silly:
1) Download latest CM-ROM
2) Copy drivers from Device X´s stock ROM to latest CM-ROM
3) Configure build.prop eg. screen resolution/DPI&co.
4) Zip and flash it
Am I right? Wrong? :cyclops::fingers-crossed:
Click to expand...
Click to collapse
I wish it were that simple
The thing is that there could be kernel and initramfs changes necessary, which is something to be built from source. Also, there are device specific files spread all over the ROM, not to mention architecture differences and lack of space. Therefore, it's better to build from source by forward porting the device
ahsanovich said:
Has there been any progress on this ROM?
Click to expand...
Click to collapse
I have a build of NamelessROM 2.0 on GDrive but it's not suitable for daily use. Also, due to the ever-increasing resource usage of Google Play Services, Android seems to be no match for our low end devices. I'm giving one last try for Omni 7.1 and if that doesn't work out, I'll scrap Android for Ubuntu Touch
Thread closed as per OP request.
Wood Man
Forum Moderator

Categories

Resources