yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] Warrenforfree:
Not only you mr. Beastmode, the truth is all of us should be happy knowing that you have fixed audio bug, and most of all we are proud to have a dev like

you who are working so hard to put this phone into action.. once again thank you for supporting us here and thank you for the rest of our SGS4G dev's behind the scene..
[Samsung Galaxy S (4G Model)] Beastmode:
Re: [ROM][4.1.2]Slim Bean 3.1.0 - SGS4G [v3][BETA]

Audio bug is fixed just tested myself with brothers sim :) release is imminent :P
[Samsung Galaxy S (4G Model)] eollie:
Re: [ROM][4.1.2]Slim Bean 3.1.0 - SGS4G [v3][BETA]

Still no ideas what is fcing the camera when you try to use Google now and search with camera. But have a lolcat.

http://db.tt/RHg2jpfh

Well crap apparently somebody is downloading the hoc a bunch and killed my bandwidth.

Here have a lolcat from pastebin.

http://pastebin.com/iuNaYcpm
[Samsung Galaxy S (4G Model)] Theraze:
Just so you know, your DB public links are disabled; too much traffic. So we can't scour your lolcat. Maybe Pastebin or something like that if Beast hasn't grabbed it yet, or if you want further scrutiny.

Edit: Looks like this might be related to recording being screwed. It crashes in line 334, and in 346 we see it calling SecCamera::stopRecord().

The backtrace around lines 364-376 (it goes on) suggests that the problem goes in the CameraService.java file. Probably. :)

Line 418 says we don't have continual focus mode, or at least it's disabled currently in the hardware.

Line 420 says it wanted to use JNI_OnLoad (for previews?) and that wasn't in the compiled file. [Edit2: Apparently this means nothing... just means there wasn't a native debug function created in that compiled file, but it's not a required method and won't cause problems on its own.]

Line 426 says that the WVMExtractor failed to load (libwvm.so). This also fails to start in 432. [Edit3: This is the Widevine Extractor, and is apparently a common problem with AOSP roms. It doesn't necessarily mean that audio won't play, but it often shows in JB ROMs with broken audio.]

Line 462 says that the googlequicksearchbox isn't supported.

Line 464 says that it's missing symbols in the libdnshostprio.so (DNS host?) file.

Edit4: From looking again, 428 seems to say that libgoggles_clientvision (line 424) is wanting to play the video recording sound file. Since Camcorder being broken is a known issue, this is probably related to the same thing.

Goggles... I mean, Search with Image, appears to be using the Camcorder input to find whatever you were trying to look up. So they should HOPEFULLY fix at the same time. :)
[Samsung Galaxy S (4G Model)] turtlepa:
Re: [ROM][4.1.2]Slim Bean 3.1.0 - SGS4G [v3][BETA]

Everytime you ask if he needs logs for current bugs, you have already answered your question.. and anymore questions.. qa thread
[Samsung Galaxy S (4G Model)] eollie:
See this is why I posted here. I missed that each time Ive looked. Or I skimmed it. Ok problem solved. weird that google now uses the camcorder and not fixed images.
[Samsung Galaxy S (4G Model)] hechoen:
Who are you even directing that at? Use the quote feature will you.
[Samsung Galaxy S (4G Model)] eollie:
Me I think..but I wasnt asking a question I was making a statement. In hopes somebody could help me figure it out.
[Samsung Galaxy S (4G Model)] Beastmode:
and....UPDATED LOL
[Samsung Galaxy S (4G Model)] johnadelic:
Torrent of Slim 3.1.0

Here is the torrent for Slim 3.1.0.
[Samsung Galaxy S (4G Model)] Jenovah:
You truly are a god beast, thank you for putting so much hard work into this phone, cant wait to see what other surprises you come out with
[Samsung Galaxy S (4G Model)] chogau1:
Is there a way to change the font? even when selecting Huge under font size in the display menu, the font is still too small. Thank you for your work
[Samsung Galaxy S (4G Model)] Beastmode:
http://xdaforums.com/showthread.php?t=2044289
[Samsung Galaxy S (4G Model)] chogau1:
Do you think that you will be able to fix the GPS? or that's a lost cause like wifi calling...Thank you again.
[Samsung Galaxy S (4G Model)] Beastmode:
/sigh

http://xdaforums.com/showthread.php?t=2044289
[Samsung Galaxy S (4G Model)] Clark Joseph Kent:
Sir, there is a reason why the OP keeps quoting the Q&A Thread for this thread, please utilize it, Thank You.
[Samsung Galaxy S (4G Model)] suck it monkeys:
logcat for video playback bug

@Beastmode

Attached is a log that I hope will help with camcorder bug
[Samsung Galaxy S (4G Model)] gregcapps:
Regarding the camcorder bug. I was looking thru the libs with root explorer and it looked like some of the camcorder encoder and decoder libs were Aries files I haven't tried swapping them out with herring but thought I would mention it.
[Samsung Galaxy S (4G Model)] Beastmode:
Just the name of them when I was trying to port over the Aries jb kernel next one will have the correct herring name though it's not workjh still
[Samsung Galaxy S (4G Model)] Beastmode:
Camcorder now records but can't play back video on phone haven't tried anywhere else.

Notification Lights issue seem to have been fixed now but I cant test much stuff that gives me notifications but on or off seems to not give reboots anymore.

Edit: so with MX player s/w rendering the recorded videos playback perfect they also play back on PC so just phone is having issues now :P

Edit2: finished implementing ezeqeel's deep idle mod and wow it makes a difference!!! For sure battery life is greatly increased :)
[Samsung Galaxy S (4G Model)] suck it monkeys:
ASS Device options force closing

Hey guys,

I have been messing around with the ROM and noticed that when you attempt to open Device Options under the ASS, it force closes. I grabbed a log.
[Samsung Galaxy S (4G Model)] Fluidification:
We know.
[Samsung Galaxy S (4G Model)] Beastmode:
Thanks for the log but it's been fixed for next update and OTA settings force closes too but I'm removing that :P
[Samsung Galaxy S (4G Model)] norman68:
Great work bro hey any chance there is away to change the status bar to show 4g , lol , but hey seriously awesome work!!! Thumbs up
[Samsung Galaxy S (4G Model)] Cooptx:
http://xdaforums.com/showthread.php?t=1904579

Look before you ask, and ask in the Q&A forum.

http://xdaforums.com/showthread.php?t=2044289
[Samsung Galaxy S (4G Model)] norman68:
have noticed when you remove a app it reboots the entire phone but the app is gone after reboot not sure if thats normal , lol
[Samsung Galaxy S (4G Model)] geekilized:
This actually happened to me a couple times.
[Samsung Galaxy S (4G Model)] eollie:
I think they are aware of this. I could be wrong tho. Couple people reported it. I have the issue too but I can never get a log. Couple other quirks that has been happening is some apps stop working and have to be force closed. That could be my governor tho Ive changed it a couple times but meh.
[Samsung Galaxy S (4G Model)] Beastmode:
Logs?

Logs?
[Samsung Galaxy S (4G Model)] Beastmode:
My git just got updated guys and gals :P

Github.com/anak1n

device tree and kernel are there :P just fork it or repo it, credit and thank :P
[Samsung Galaxy S (4G Model)] FBis251:
Already grabbed! :D Thanks for the heads up.
[Samsung Galaxy S (4G Model)] Beastmode:
That's what she said lol sorry had to

But yea it's all there should have a nrw proton JB this week and an update to cm10.1 and slim4.2 that's right 4.2 lol
[HTC One X] zottel1993:
How is it possible that some devs using an jelly bean kernel for there roms? I read that htc doesnt public the source...and why cant we use these kernels for aosp?
[HTC One X] Mr Hofs:
Correct me if i'm wrong but there is only one JB kernel and its the stock one. They can use that one because it was in the leaked Rom/Ruu.

Or am i misreading the question.
[HTC One X] matt95:
for the sense rom there is only the stock kernel, for the AOSP AOKP and CM10 there are different kernels...
[Xperia Arc Android Development] jerpelea:
hy all

this is an project starter for android 3.4 kernel development for all msm7x30 mogami devices

sources are hosted on

https://github.com/freexperia/android_kernel_semc_msm7x30

br

J
[Xperia Arc Android Development] jerpelea:
Project Status

- we got initial branch after diffing lost of branches

M7630AABBQMLZA203029A

https://www.codeaurora.org/gitweb/q...it;h=4b2b84c6a0b6d29864e982a7aecc223acfd2eaa1

forked to our git and with mogami patches aplied

https://github.com/freexperia/android_kernel_semc_msm7x30/tree/M7630AABBQMLZA203029A

latest CAF tag for 7630 not usefull for now

https://www.codeaurora.org/xwiki/bin/QAEP/release

"November 16, 2012 M7630AABBQMLZA40701070 - msm7630 - M7630AABBQMLZA40701070.xml - 04.01.02" android 4.1
[Xperia Arc Android Development] jerpelea:
ETA

depending on problems and developers that will join

from 6 months to NEVER
[Xperia Arc Android Development] CosmicDan:
This is a bold task. Perhaps you could look at the developments of irii-soft (and some others), they have replaced some crap Sony-specific code with generic wrappers. Main obstacle if I remember is memory maps now, there was an issue with partition maps but ATAG can be easily over-ridden via kernel command-line.

Getting it to boot should be trivial, sound and video will be difficult, and RIL may be never working due to lack of sources. Regardless, all the best. When I have more time I plan to help irii with his work on a "generic" 2.x kernel newer than what we have (because 3.x seems outrageous at this point).
[Xperia Arc Android Development] Boudin:
Is there a wiki, a forum or something like that lists all the non-standard things that have already been found ? (some base of work to do)
[Xperia Arc Android Development] CosmicDan:
Easy to do yourself - download official SEMC kernel source and diff it with the same version of the linux baseline kernel. So to port to newer kernel you can isolate or "extract" the specific code that has been added and changed, and merge or "inject" that into a newer kernel. Easier said than done though, there are massive changes even in linux kernel revisions (0.0.x.0) - let alone alone new majors and minors (x.x.0.0).

There wouldn't be a wiki or anything of this research, because documenting it all would take an unrealistic amount of labor. Considering there are only a small handful of developers capable of it, there's no point. Besides, that's what GitHub and commit logs are for.
[Xperia Arc Android Development] The Gingerbread Man:
To FXP team,

I don't know if you know or not or even got this far in the development stage but I just wanted to point out a couple of things which may or may not help you...

So with the 3.4 kernel brings newer WiFi drivers which will give a better connection signal on wpa2 security but you might find that devices won't be able to connect to open security networks and WiFi hotspot will probably be broken. I'm posting this as on my gnex using custom kernel (FrancoFransico) he incorporated the 3.4 WiFi drivers a few times and broken hotspot and not being able to use open security WiFi networks were repeatedly reported problems.

I think it may be something hardware specific which allows these features to work on the 3.4 WiFi drivers specific to the nexus 4? You may have more luck trying the 3.0.xx WiFi drivers and getting those to work fully.

Best of luck to you guys!

Sent from my Galaxy Nexus
[Xperia Arc Android Development] CosmicDan:
I'm pretty sure wifi is way down on the priority list, not to be rude but really - who cares about that now. Priority list would be like this:

(1) Get it to boot

(2) Fix primary/critical hardware-specific code for msm7k and qcom platform (display, audio)

(3) Fix RIL

(4) Fix secondary hardware (sensors, bluetooth, wifi)

One step at a time. Getting wifi will probably be trivial because bcm sources are part of the mainline kernel.

With that said, I'm unsubscribing from this thread now. There is massive work to be done and I can see this thread is just going to be filled with posts that have nothing to do with actual development.
[Xperia Arc Android Development] iridaki:
All non-dev related posts, and especially "Thank You" posts, will be deleted without further notice. If I have to delete 5 pages of useless posts again, this thread will be locked.

Thank you!​
[Xperia Arc Android Development] adridu59:
We have tried for a long time already (as you may already know).

https://github.com/adridu59/semc-msm-3.4/commits/master

https://github.com/adridu59/semc-msm-2.6.35

https://github.com/adridu59/android-msm-2.6.35

https://github.com/ExPeacer/CAF_android-msm-3.0/commits/master

https://github.com/ExPeacer/CAF_android-msm-2.6.32

Have fun with it anyways. :)
[Xperia Arc Android Development] thomas1991_12:
Whats the progress so far on this? Bootable already?
[Xperia Arc Android Development] scholbert:
Hey tom3q,

thanks a lot for leaving some useful statements here!

I digged for some base kernel for a while.

Found a chromium msm kernel 2.6.32.9 at codeaurora (i know this is not Android).

Anyway, the diff against stock was ~30MB... quite too much.

Like i assumed many basic things are missing as well, so too much to start from.

I guess, i'll step through the other projects... might try 2.6.32-rc8 from the msm tree... just for fun of course :angel:

Nice point... i like these hardware hacks and asked about testpoints for UART3 on the Pro mainboard a few days ago.

It's mentioned and so far i got it, initialized in stock kernel as well. Unfortunately no-one seems to know anything about these testpoints.

Anyway i don't want to spam this thread, so thanks for your attention ;)

Regards,

scholbert
[Xperia Arc Android Development] jerpelea:
hy

scuse my ignorance

but

HOW do you compile an kernel ?

and maybe someone can explain what is the difference between bring-up and port
[Xperia Arc Android Development] voyteckst:
I would say that porting is moving and correcting sources from 2.6.32 kernel in our case into 3.x. And bring up is writing particular drivers from scratch?

Sent from my Nexus 7
[Xperia Arc Android Development] jerpelea:
ok

nice explanation

look on first page
[Xperia Arc Android Development] jerpelea:
diff is 5mb on proper tag

pushed on github
[Xperia Arc Android Development] jerpelea:
nice to see so many developers trying to help
[Xperia Arc Android Development] tom3q:
Sorry to throw my 3 cents again, but seeing the repository on github, I'd recommend you to use some time to go through Git Immersion. Even if it takes some time, it will simplify your further work, as Git used properly can really make many things easier.

Otherwise, the diff itself looks mostly fine as a starting point, although some of the differences can be probably eliminated.
[Xperia Arc Android Development] jerpelea:
sony added too many changes to be usefull

since there are several api changes on 32->3.x diff is no good

we have to start from clean board-7x30 and populate devices porting drivers 1 by 1

we have to try an device bringup based on sony changes
[Xperia Arc Android Development] CosmicDan:
That's pretty darn good. Turbo Kernel for Play/Neo L only has 379MB RAM without 720p.
[Xperia Arc Android Development] Galileo:
Sorry for the noob question, but you mean overall right? not 395 free out of the avalable memory?
[Xperia Arc Android Development] CosmicDan:
Of course I ment total capacity, these devices only have 512MB and 60-90MB is reserved for the kernel.

Anyway, RAM optimization is not really on topic for 3.4 development.
[Xperia Arc Android Development] Galileo:
I see, thanks, and yeah i undesratand, first comes building the kernel, Optimizations (If anything planned) comes afterwards. I guess it is hard enough as it is.
[Xperia Arc Android Development] n1kolaa:
first macking it bootable,then fix all hardwere to work,then comming some tweaks at the end :)
[Xperia Arc Android Development] Galileo:
Yeah, i just hope more developers could join in on this project, im willing to wait 6 months or more for the 3.4 kernel, but the NEVER in black font kind of makes me feel uneasy hahaha.
[Xperia Arc Android Development] Yovecio:
A little question(...i don't want to spam :) ) , i've read that recently galaxy s plus have a 3.4 working kernel so i want only to ask if we can use it partially to make all work easier or it's useless?

Thanks in advice!
[Xperia Arc Android Development] CosmicDan:
Irrelevant. Galaxy S Plus =\= Xperia 2011.

People need to stop with the "So-and-so device has 3.x kernel, can we port that?" questions.
[Xperia Arc Android Development] Yovecio:
Ok but have same chipset...
[Xperia Arc Android Development] CosmicDan:
So do many Mac's and Windows PC's. So does the Commodore Amiga and the Sega Genesis. So do some microwaves and TV's. "Chipset" (Soc) is not the only hardware in a device. You'll need an education on computer engineering to understand why and I won't go into it since it's off-topic.

Besides, if there was anything in that kernel that *might* help, one of the developers would already have noticed and be on it. This is why developers rarely reply to posts like this - because there's nothing to say that wouldn't be offensive or sarcastic.
[Xperia Arc Android Development] solid7:
noob question

1) Xperia J get Android 4.1.2 Jelly Bean and had kernel 3.4 and its the same chip of our 2011 devices

2) Samsung galaxy s plus had kernel 3.4 and its the same chip of our so could they help us (this one is been discussed many time i think)

3) where we r from this project ((alpha - beta - RC stage))
[Xperia Arc Android Development] n1kolaa:
1) not same we have msm7x30 , j have msmx27a

2) same chipset but, not same board and manfacure

3)this project is pre alpha and dont ask for eta!!
[Xperia Arc Android Development] scholbert:
... what's the state we're in?

Hey there,

just a short statement in general...

I'm very impressed about the work of the FXP team in the past and present, there's no doubt.

The information politics of the FXP team could be improved there's no doubt as well.

Apart from "we got boot", there'd been no extensive comment on anything here.

Everybody is shouting for more developers and pointing out "check this, check that", but waits for things been done.

If no one feels responsible, nothing would happen.

I'm in doubt that most ever had a look at what we already got and what is missing.

The FXP git tree is a good starting point already, but still misses some essential parts to boot on a regular phone.

So instead of having the the situation with people asking dumb questions and waiting for things to come up...

maybe some get infected by the opensource virus and the DIY spirit.

Take this as an advice to anyone who ever looked into a kernel source once and a got a slight idea how to set things up:

- we may easily create a branch for open development and call it community branch

- we could easily create a new thread for open discussions by refering to this thread and keep this thread clean

- we could start collecting old skool patches for the community branch, in case someone has trouble with the git system

- noobs should always read and learn

I suggest to have a look at the board-semc_mogami.c file first.

This is one of the key elements for getting anything to work on the Xperia 2011 series.

Right now it's just a bare copy of board-msm7x30.c and it needs work.

My guess is that FXP really wants to start from scratch and keep things close to the aurora branches.

This way it could be possible to leave some Sony hacks out of the code and keep it closer to mainline.

If you step back in the 2.6.32 (latest stock kernel for Xperia 2011) and compare both files you see what i mean.

There could be as well a path to hack things together, keep Sony specific parts and port things in a more convenient way.

We need at least check every function call in the board-semc_mogami and compare it with new kernel.

This will still lead to a quite hugh amount of things to consider and to check.

That being said i'm in doubt that i will find some sparetime slots to contribute valuable parts myself.

E.g. i started to work with the board-semc_mogami.c weeks ago, but have to admit that time is lacking to get things rolling.

Anyway, take this as a personal statement. Neither i wanted to blame anyone nor should this sound rude in anyway.

Just my thoughts, so thanks for your attention!

Have fun,

scholbert
[Xperia Arc Android Development] n1kolaa:
look here naa is looking for new phone

he is one ho port 2.6.32 kernel to x8,x10 mini,pro and very skilled developer

https://twitter.com/birbilakos

from twitter

ps we can use some codes from xperia s

sory for offtopic

EDIT: i sow some our open sources on github :) (android_device_semc_mogami-common)
[Xperia Arc Android Development] n1kolaa:
THE DEAL

so i got deal with nAa,so set his paypal as my on xda and if you donate to me(him) he will bay xperia arc to develop on(nobodyAtall)

chers n1kolaa
[Xperia Arc Android Development] tinyXperia:
A few post up all this is explained! Same cpu is not same board!!!

(And nikolaa says it's not even the exact same cpu)

Via Tapatalk
[Xperia Arc Android Development] n1kolaa:
Can we mont system as ext4 ?
[Xperia Arc Android Development] nickholtus:
No and not related to this
[Xperia Arc Android Development] nickholtus:
As answer on n1kolaa question, no we cant mount it and not related to this
[Xperia Arc Android Development] CosmicDan:
ext4 is only useful for eMMC devices. Yaffs2 is better for NAND devices.

Sent with Tapatalk
[Xperia Arc Android Development] ApriliaM3:
Guys please try and keep on-topic here and resist the urge to argue and inflame the situation.

I'm the 3rd Moderator that has had to come here and cleanup in a short amount of time and I'd prefer not to have to return for the same reasons...

Thanks.
[Xperia Arc Android Development] kemoba:
So guys i was browsing through XDA and i found this guys github https://github.com/erik96?tab=repositories , he made the 3.4 kernel for SGS+, i had a quick browse through some of his gits and it seems that there is some code for our chipset going, i was thinking that the devs can kang some stuff for it ?
[Xperia Arc Android Development] demolatorul:
We talked about this few pages back, if you have read some pages back you would already know the answer
[Xperia Arc Android Development] jader13254:
AW: [development]-kernel 3.4-freexperia

Seriously? Already 29019 people before you asked about Galaxy S 3.4 Kernel. NO, it doesn't help to have the same soc. Same soc = not same hardware. Stop asking about it, read previous useless posts, and let fxp do their work.
[Xperia Arc Android Development] n1kolaa:
we have only same hardwere with one v but also not usable sources, i realy dont know way :(
[Xperia Arc Android Development] CosmicDan:
Dunno why they bother. The Xperia 2011 series is obsolete and all experienced users have moved on - as evident by this entire page being troll posts.

Users need to know their place. If you're not developer, enough with the posts. Little do you know that it causes developers to work less and ruins the spirit of XDA.
[Xperia Arc Android Development] adridu59:
Unsubbing.
[Xperia Arc Android Development] caqo71:
I just wanna know if Xperia X10 devs/users did acomplish to buld a kernel above of the sonys one. If this thread existed on X10 times, then all the noobs could shout theyr mouth. Let the devs work.:good:
[Xperia Arc Android Development] bluestricker_21:
Hello developers, first of all i don't want to post here because i know

Some of you will get mad but i want to know what is the REAL PROGRESS now?

Any news? FXP is not posting any changes about the development is he already stop

Or just busy doing with his cyanogen?

Edit: i see fxp github about the development but it was not changed for the last 3 months.hs

Is is it really in progress or its just you guys arguing witj each other?
[Xperia Arc Android Development] tangosierra_:
FXP will post here if there is any progress. Thheir git could be not updated for many reasons. They have lives too.