yashsingh1/xdaforums huggingface dataset:
[LG Thrill 4G] jznomoney:
1) What is all this stuff about the baseband? Call me a noob, you may, because I am, but my last phone never had to deal with that whenever I was upgrading the ROM.

Baseband is the firmware that runs the radio on the phone. Basically the part that deals with the connection to the cell network.

2) V20C, V20P... I'm reading and beginning to grasp some of this, but what exactly ARE those? Are those just ROM release/version numbers?

They are the rom release version numbers. Mostly they are revisions based for the network provider. IE: v20p is the at&t revision.

3) Cyanogenmod - I'm quite fond of this line of ROMs, and would like to go to that relatively problem free (when the stable release is out). There are conflicting reports on what we need to do to achieve CM7 on our phones.

Yes cyanogenmod varies on our device. Since LG dropped the needed code arcee will be able to merge the LG Thrill/Optimus 3D into one release. He already released a test version. Check out his post on google plus for the link. You will need the v20p rom installed and rooted for that version.
[Android Q&A, Help & Troubleshooting] lunchboxVA:
I was wondering if there was a way to modify the s78 enable touchscreen script so it will work on my phone...or if there is a way to add the directories it needs to work to the SYS directory...

the script is:

echo 7035 > /sys/class/touch/switch/set_touchscreen;

echo 8002 > /sys/class/touch/switch/set_touchscreen;

echo 11000 > /sys/class/touch/switch/set_touchscreen;

echo 13060 > /sys/class/touch/switch/set_touchscreen;

echo 14005 > /sys/class/touch/switch/set_touchscreen;

and is supposed to alter the touch screen sensitivity...I noticed it is included in a ROM i was using by the dev...but when i try to run it it errors out because it cannot create the directories as needed...

I have a rooted epic 4g touch

please let me know if any more information or details are needed

thanks in advance
[HTC EVO 3D] geordie 34:
Not sure it this was suppose to happen but just to let you know what has just happened to me. I just rooted my phone using HTC SUPERTOOL installed busybox etc, went into my bootloader and still had LOCKED but s-off hboot version 1.49.0018 I then downloaded the HTC Europe RUU from the development forum, went very well, so I checked my bootloader again, and it had changed to LOCKED s-off 1.49.0007.

Not sure if people were aware of this or its only happened for me. I then ran the OTA update which has now put it back to LOCKED s-off 1.49.0018.

Has this opened anything up
[HTC EVO 3D] G.Newton:
If you snoop around, someone else has this issue as well but he had a GSM Evo 3D.
[HTC EVO 3D] geordie 34:
Mine is gsm also I seem to have permanent s_off no matter the bootloader and ota update
[HTC EVO 3D] lilvfr400boy:
Yep me too I had 1.49.0012 I downgraded too 07 soffed with rev then relished stock 07 and did official ota .0018 update still s off and re rooted

sent from a galaxy far far away where I actually understand the mods I do to my phone thank fu*k for devs
[Optimus One, P500, V General] Deone Word:
My phone has a major problem. I'll explain the steps I took to screw it up this badly.

1.) Root phone and install a ICS rom

2.) Market doesnt work so I reinstall another market/vending.apk app from mediafire

3.) Market still didnt work so I install another rom

4.) Then I use that rom and rom manager is gone so I install another one I downloaded form mediafire.

5.) That rom manager only verifies my phone as a optimus c but i still installed clockwork mod

6.) The version Clockwork mod does not work

7.) I installed Xionia recovery instead

8.) I accidentally, in xionia, do a factory reset that bricks my phone.

9.) I could still use adb to force files on and try to recovery the phone by flashing files

10.) I flash a recovery image file and now here is the HUGE problem

11.) MY PHONE WONT BOOT UP AT ALL, ALL THAT SHOWS IS THE LG SYMBOL AND THEN BLANK SCREEN. WHEN I HOLD DOWN,POWER,HOME IT DOES THE SAME THING (BLANK SCREEN). AND WHEN I TRY TO USE ADB I GET THAT MY PHONE IS CONECTED BUT,

c:\adb devices

List of devices attacched

A100001944D988 recovery

Then I try ADB shell

C:\adb shell

But I get

/ #

and i cant complete any commands

when i try adb remount

C:\adb remount

remount failed: Invalid Argument

Can Someone Please Help
[Optimus One, P500, V General] dsuffern:
Same issue
[Optimus One, P500, V General] Deone Word:
Maybe the Virgin Mobile Store will just give me a new phone cause there is no actual proof that I rooted the phone.
[Optimus One, P500, V General] sachin kamboj:
Before trying this method be 100% sure that recovery is not working hold volume down + power + home continuously for around one minute if u get fastboot error, follow this - http://xdaforums.com/showthread.php?t=1088046thread but still if u see nothing u have to use kdz method http://xdaforums.com/showthread.php?t=883314 or see this link for a picture guide - http://xdaforums.com/showthread.php?t=1060121
[Android Q&A, Help & Troubleshooting] NoobSEowner:
lol, i know this sounds noob, but i am confuse, i got xperia ARC S which is the android version is 2.3.4 and number which is I dont know what it is and it's shows 4.0.2.x.x.xx

which one is the real android version? :S i see many thread talking about Ice cream sandwich and the ICS version is between 4.0.1-4.0.3, but still my android version is 2.3.4 gingerbread? am i outdate? =.= also my phone specification shows that i am using the 2.3.4 gingerbread at here http://www.gsmarena.com/sony_ericsson_xperia_arc-3619.php

and this link make me more confuse about ICS and gingerbread : http://developer.android.com/guide/appendix/api-levels.html

sorry for my english
[Android Q&A, Help & Troubleshooting] melvinchng:
4.0.2... should be the version number.

Android version should be 2.3.4.

Those newer phone can run Android 4.0. Google only release OS update officially to Google phone, nexus s, nexus one, galaxy nexus. Other than this devices, you have to wait for your manufacturer to update your device.
[Android Q&A, Help & Troubleshooting] NoobSEowner:
btw, what is the latest version number and android version?
[Android Q&A, Help & Troubleshooting] NoobSEowner:
Hello?

(i know it's too short)
[Android Q&A, Help & Troubleshooting] Theonew:
Are you talking about it for your device or in general?
[Android Q&A, Help & Troubleshooting] NoobSEowner:
General sir :d
[Android Q&A, Help & Troubleshooting] Theonew:
Version number varies by device, but the latest android version (at least up to the date of this post - will be updated eventually :D) is Android 4.0.3 Ice Cream Sandwich.
[Android Q&A, Help & Troubleshooting] NoobSEowner:
why my phone has 2.3.4? and some number shows 4.0.2? @.@ im starving zzz
[Android Q&A, Help & Troubleshooting] Theonew:
The version number (OF THE DEVICE) and the firmware version are different.
[Android Q&A, Help & Troubleshooting] Felimenta97:
Arc S will get Android 4.0.3 by may, as SE promised.
[Fascinate Q&A, Help & Troubleshooting] CountryBoy_71:
I'm hoping that I am not just asking the same question for the 100th time but here goes...

I have a TELUS Samsung Fascinate. I rooted this with SuperOneClick, used the GaryS Unlock and had it running on Bell. Then, I upgraded the OS to 2.3.3 using Kies and it broke the root but unlock is still good.

I've been trying to fix the root now and SOC hangs on step #6. Doing some research I discovered that 'su' was no longer in the system/bin or xbin folder. I found a tutorial telling me to put this file back. Obviously I can not just paste this file into the system folder because of the permissions. I tried using ADB Shell but I am having problems changing the permissions...this is where I need some help?

Can someone help me figure out how to get this file back on the phone?

Please forgive me if I've forgotten any details.

Thanks
[Fascinate Q&A, Help & Troubleshooting] MrManiacNF:
There is a new superoneclick? I don't know if it works, but I would imagine the problems have been addressed.

This is will get your root for you.

xdaforums.com/showthread.php?p=16841605

Hope it helps!

-Maniac
[Fascinate Q&A, Help & Troubleshooting] jpmccarthy:
Also do a search for T959D and Speedmod kernel - there is a way to get root that way, but I hear S1C works now.
[Fascinate Q&A, Help & Troubleshooting] MrManiacNF:
My post will take OP too the speedmod tutorial.

If you do get superoneclick to work, want to drop a line to let me know.. then I will know for future times when people ask me.

thx

-Maniac
[Fascinate Q&A, Help & Troubleshooting] Rabid_Gypsy:
I can say for sure, that the newest version of S1C does work. Tried it today.
[Fascinate Q&A, Help & Troubleshooting] MrManiacNF:
Awesome! thx.
[Desire Android Development] Chaosz-X:
See page 19 for the seventh build.
[Desire Android Development] Kryziek:
Good job! Nice and clean in a new topic. KUTGW!
[Desire Android Development] StillTheWatcher:
Freaging sweet!

(sorry for spam but this is exciting)
[Desire Android Development] danarama:
Excellent stuff.

So will that mean close to full HWA?
[Desire Android Development] pnw:
If we're running any of the ICS builds which have the hardware hacks, this applies, right?
[Desire Android Development] Chaosz-X:
@rootSU: I think it does, because it scores almost the same as GB Sense ROMs, and it gets pretty decent FPS at Quadrant (certainly smooth enough), so I think it works fine.

@pnw: haven't tested that, but you can give it a try, it seems pretty logical that it would help :)
[Desire Android Development] theyau:
Can't wait for the 3.0 kernel
[Desire Android Development] mattmanwrx:
I flashed this on the p2 build, but my wifi would not turn on... I reverted back to my nandroid right before the flash... :)
[Desire Android Development] Sandvold:
chaoz tried including the wifi module you use in the kernel in the system/lib folder? can't find it there on the newest kernel. This messed things up for tristan earlier
[Desire Android Development] Chaosz-X:
Oh crap, forgot to supply the bcr4329.ko indeed.

I'm going to try to get a running 3.0 by tonight, if I don't have it finished this evening, I'll upload the WiFi module from the build (using 2 different OS's to work on, Linux for compiling, and Windows for everything else, and working in Win is much easier for me ;p)

Edit: beginning with the really lame methods of getting 3.0 to run, first attempt is done I think, just copied over files, and modified some of them, nothing really special, starting compiling in 5 minutes.
[Desire Android Development] *child:
I flashed over p2 with the camera fix and the camera no longer works. Should I reapply the camera fix?
[Desire Android Development] mattmanwrx:
But does your wifi work? It didn't work for me...

Not too sure about the camera... it should work... as the added is just libs... the kernel does look at the libs, but doubt it would make a difference... just my guess...
[Desire Android Development] Anon87:
Wifi did not for me. Camera worked but I didn't test it extensively.

Sent from HTC Desire
[Desire Android Development] jozef710i:
Camera and wifi doesnt work But HW ac. is fine more speed
[Desire Android Development] *child:
Wi-Fi also does not work
[Desire Android Development] texasice:
Chaosz-X first of all, thanks for the work you've done so far. I believe i can port it over to the n1 using the zip you uploaded. Second, please learn git so you can push your changes to github. (i know you said you hate git but, youre developing a kernel; in comparison git is way easier to understand) It will be much easier for other devs to follow your progress, and port your changes to other qsd8k devices badly in need of hwa. ;)
[Desire Android Development] dirwdirw:
cant wait 3.0 kernel for n1
[Desire Android Development] bunnahabhain:
How could he even develop a linux kernel if he is better in using windows? Dont you have to be a kernel dev to do those things?

Some devs are crossing strange lines - 4 sure :D. Hope you get it done for our Nexus ONE my friend ;)

cheers
[Desire Android Development] vasili_defy:
sweet..kernel 3.0!!

waiting ..waiting..:D
[Desire Android Development] danarama:
People start with windows at a young age
[Desire Android Development] Kalashnikitty:
wuhu im horny :eek:
[Desire Android Development] itsy:
Don't distract him, I want this now!! :-P
[Desire Android Development] Chaosz-X:
Still a little problem, Kconfig still gets called to modify the .config, and then it removes all Bravo-specific stuff. In other words: the system wants to change the .config file each time I want to build. I need to disable Kconfig or suppress it to not change my .config. Looking for a solution :)
[Desire Android Development] K900:
Use make oldconfig
[Desire Android Development] Chaosz-X:
Tried it, it adds it's own lines from 3.0, but when I check the file, all my previous edits are lost again.
[Desire Android Development] K900:
That's strange...
[Desire Android Development] itsy:
Stupid question (don't know anything about building stuff^^):

Can't you just rename Kconfig or make your .config file write-protected?

There needs to be a way somehow ;)
[Desire Android Development] JeckyllHavok:
Hi there, i'm an absolutly noob in kernel things but what about that one, line 46:

http://lxr.linux.no/linux+v2.6.34.1/Documentation/kbuild/kconfig.txt
[Desire Android Development] Chaosz-X:
Build 7: http://api2.ge.tt/0/9E4FvzC/0/blob/download

Changes:

-Set some stuff for Bravo

-Modified the .config, so it compiles properly

-And much more stuff I don't remember anymore
[Desire Android Development] dk_zero-cool:
Great, testing it now.
[Desire Android Development] kri5:
Any way of contacting you by irc, or some other im system?

Interested by helping you on you're spare time.

PS: I got knowledge on build system (more or less), and C devel.
[Desire Android Development] blubberheld:
doesn't boot, stuck on splash...

****...
[Desire Android Development] Chaosz-X:
Hmm, still not booting?

Edit: also, still not able to logcat?
[Desire Android Development] blubberheld:
nope, for about 5 mins now, so i don't think the device is getting it done...
[Desire Android Development] dk_zero-cool:
Sorry but same as yesterday. It get's nowhere, and no logcat.
[Desire Android Development] Chaosz-X:
Alright then, I think I'm sure which line breaks it from booting.

static void __init qsd8x50_init_irq(void)

{

msm_init_irq();

msm_init_sirc();

}

The first line, with init_irq() is the one which causes errors. In other words, my guess is that the way of initializing IRQ (interrupt requests) in 3.0 changed. So people, look into other source codes of other devices (you have to look in the board-<socname>.c file, and see how the part of _init_irq(void) is done there. In my case, this file is board-qsd8x50.c, and it will differ for other devices, so you have to find out which file is responsible for that device, find the spot where init_irc is called in the boardsocfile, and check how it is called there. If you find any resource or site, post it here please, or PM (even better, so I can keep it organized).
[Desire Android Development] RedBullos:
Hi,

look here:

http://lxr.free-electrons.com/source/arch/arm/mach-msm/board-qsd8x50.c

I hope it will help ...

Line 179 is the init_irq
[Desire Android Development] RedBullos:
This looks interesting too:

http://code.google.com/p/bricked/source/browse/arch/arm/mach-msm/?repo=tenderloin&name=ics-exp
[Desire Android Development] Chaosz-X:
Looks like the issue is fixed by including a few more header files. Recompiling now with the right IRQ fix, meanwhile taking a shower. Expect an update in half an hour :)
[Desire Android Development] kuyam:
Not that I mind at all, but if you don't have a desire, why work on a kernel for it ?:) Or is it just that you don't have it right now..
[Desire Android Development] Chaosz-X:
My Desire was broken for a while, and now I have it back already, but I'm working for a small company and that means I can't risk being unavailable for business partners. That's why I can't flash stuff when I'm not sure it works: setting up the preferences on my phone etc., takes some time, which is pretty important to me.
[Desire Android Development] TheYang:
get a cheap-ass 10$ Phone, and switch the SIM for development :o
[Desire Android Development] Chaosz-X:
Contacts, messages, files on my SD, no way I can switch to another phone.
[Desire Android Development] SilverHawk2:
people stop beeing so rude! You can be glad that we have such a fine a kernel dev !
[Desire Android Development] MrPadie:
I look forward to getting this up and running on the HD2 once you've got it going!
[Desire Android Development] TheYang:
wasn't meant rude in any way, just a suggestion of the way that seemed the easiest (and best) to me

I'm very thankful for his time already, and will be even more when the kernel actually boots ^^
[Desire Android Development] kuyam:
Ran into unexpected trouble? i'll keep my a2sd-less ics ready to test tho :)
[Desire Android Development] Chaosz-X:
That msm init irq thing is still messing around, and I tried a lot. I'm uploading the kernel source within 1 hour, and hopefully someone else can fix that issue with the IRQ init. And when that's done, I think it should generate a working zImage.

Edit: that will be tomorrow, going to bed now.
[Desire Android Development] zaher.bahouth:
I hope this could help in any way

https://github.com/Ezekeel/android-3.0
[Desire Android Development] Chaosz-X:
Uploaded the source code to https://github.com/Chaosz-X/Dirty

Would be much appreciated if someone else could continue the work, as I'm really busy with school the coming days. Also, read the README to know about the issues etc. :)
[Desire Android Development] zaher.bahouth:
here is _thalamus kernel for Nexus S.. if this could help

https://github.com/thalamus/android-kernel/tree/S5PC210
[Desire Android Development] Thömy:
MACH_TYPE in arch/arm/tools/mach-types is missing. You probably never noticed it because the following code in board-bravo.c was never build.

#ifdef CONFIG_MACH_BRAVO
MACHINE_START(BRAVO, "bravo")
#else
MACHINE_START(BRAVOC, "bravoc")
#endif
.boot_params = 0x20000100,
.fixup = bravo_fixup,
.map_io = bravo_map_io,
.init_irq = msm_init_irq,
.init_machine = bravo_init,
.timer = &msm_timer,
MACHINE_END

This part is essential.

Also is this based on msm-3.0 or Googles android-3.0? It looks like it is the latter one.
[Desire Android Development] eirikgu:
Shut up. Respect the amazing job he is doing. If you think you can contribute, do so, but stop *****ing.
[Desire Android Development] K900:
Probably because it never booted anyway so there's not much to do here for non-devs
[Desire Android Development] Chaosz-X:
@the one who said I'm a retard: STFU, go ahead and show us how to build this kernel flawlessly. Can't do that? Then just appreciate people for their work for the community.

@Thomy: sounds good, can you fix it? I don't have much time atm for work.
[Desire Android Development] kri5:
Just added irq-vic.o to Makefile in arch/arm/mach-msm/Makefile on the line of the qsd8x... board, and seems to compile
[Desire Android Development] animehq:
Compile ok, but does it boot ?
[Desire Android Development] Thömy:
Nope, it won't.

That won't make it a working kernel. But you gotta start somewhere, don't cha? I still don't know if it's all worth the effort and what the benefits will be. Still much work to do. The board-bravo* files are also not build by the Makefile and you just include board-bravo.h in some other file.

Here is a Git repository with the orignal history: https://github.com/thoemy/android-3.0/tree/chaosz-x

And here are the changed made by him: https://github.com/thoemy/android-3.0/compare/android-3.0...chaosz-x

For those who are interested.
[Desire Android Development] Chaosz-X:
I thought it was calling all the Bravo files by CONFIG_MACH_BRAVO=y in .config, what else do we have to change to include the files properly?
[Desire Android Development] paolo-red1:
from Nexus One forum:

link: http://xdaforums.com/showthread.php?t=1366897&page=192
[Desire Android Development] MightyBen:
This sounds great. :-)
[Desire Android Development] Thömy:
Look at the Makefile in arc/arm/mach-msm/. This is where files are included. Add something like this:

obj-$(CONFIG_MACH_BRAVO) += board-bravo.o board-bravo-panel.o
obj-$(CONFIG_MACH_BRAVO) += board-bravo-keypad.o board-bravo-mmc.o
obj-$(CONFIG_MACH_BRAVO) += board-bravo-rfkill.o htc_wifi_nvs.o htc_awb_cal.o
obj-$(CONFIG_MACH_BRAVO) += board-bravo-wifi.o board-bravo-audio.o
obj-$(CONFIG_MACH_BRAVO) += msm_vibrator.o
obj-$(CONFIG_MACH_BRAVO) += board-bravo-microp.o
obj-$(CONFIG_MACH_BRAVO) += board-bravo-tpa2018d1.o
obj-$(CONFIG_MACH_BRAVO) += board-bravo-smb329.o

The variables here valuate to y,n,m or nothing. And based on that the files are build or not.

Every name of the *.c file should appear in the Makefiles somewhere in the tree.

The bravo-board.c now includes bravo-board.h and so on. Don't modify the board-qsd8x50 files. Everything Desire specific should be in the board-bravo files.

And a personal appeal: please learn Git :). Don't hate it, try to love it! At some point your life will be so much easier (at least in respect to kernel coding). The documentation is good and searching for something in Google will almost every time have a correct Satckoverflow answer at the top.
[Desire Android Development] Sandvold:
https://github.com/drewis/tiamat-kernel/compare/updates

That what drewis (n1) did to get it to boot i guess. Maybe helpful
[Desire Android Development] Thömy:
He is porting the important stuff back to 2.6.38. In this case I don't think it will help. But good to hear that he is close to have that working. The user will probably never notice if it is the 3.0 kernel anyway :).
[Desire Android Development] fritsypeij:
While that might be true, you'll never know what happens in the future.. At least our old devices will get more future proof, and developers are getting used to developing for / with the newest kernel :)
[Desire Android Development] Thömy:
Yep, maintaining a Kernel that has a lot of backported stuff is way harder. But Android 4 is probably the last version we will get anyway.

---------- Post added at 03:18 PM ---------- Previous post was at 02:59 PM ----------

Chaosz,

here is a Git branch with some very basic stuff to get the kernel to boot. I left out anything that was not needed. It just resets the Desire as soon as possible and writes the kmsgs to a ram console. The contents of the ram console are then saved across a reboot by the next kernel that has CONFIG_ANDROID_RAM_CONSOLE=y (which should be about every kernel out there) and accessible under /proc/last_kmsg. Because the ram console is not cleared it may contain messages from other boots. Just look at the beginning.

I did this a while back but didn't upload it anywhere. It is not rebased on the last changes but may be useful for you if you continue to work on this kernel.

This kernel will do nothing useful! Except if you want to develop it further. It is just an example of the first steps needed when adding a new device. Don't flash that kernel with a boot.img! Use fastboot to boot it.

The branch is in the same repository as the other branch I created for your changes (https://github.com/thoemy/android-3.0/commits/reset-test).

To build:

ARCH=arm make bravo_test_defconfig
export PATH="/path/to/your/toolchain/bin:$PATH"
make ARCH=arm CROSS_COMPILE=arm-eabi- EXTRA_AFLAGS=-mfpu=neon

I used the android-toolchain 4.5-2011.09 from here http://www.linaro.org/downloads/1109/.
[Desire Android Development] Chaosz-X:
I doubt that ICS will be the last version we get, as AOSP is far from heavy, and if we can run Runnymede ROMs, we're pretty save with future versions of Android.

BTW, thanks for your post, I'll look into this tonight :)
[Desire Android Development] kuyam:
It's funny, because so many people prefer (slightly modded) AOSP over sense/other skins.
[Desire Android Development] fritsypeij:
I never really did, but what Google has accomplished with their new style (including Google Apps) is really amazing and sets (if you ask me) an example in how clean and unified interfaces can get. I'm pretty exited to use all of their new products :)