yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] Fluidification:
sorry getochkn, I happened to make a bad change, and your going to need to recompile after mka clobber since there are changes to board config.

I fixed those changes back in github, so when you run repo sync again, it will pull those in.
[Samsung Galaxy S (4G Model)] getochkn:
so what steps would I need to resync then, that was my 1 question out of the 2 I had. lol.

EDIT: What did you change, this is booting great so far. lol.
[Samsung Galaxy S (4G Model)] Fluidification:
oh... you started the build more than 2 hours ago, which means that you didn't pull in my garbage!

So, you didn't get the new gps fix test... and the other garbage.

to start from scratch though, you need to run the following command.

cd "cmdirectory" && repo sync && . build/envsetup.sh && lunch cm_galaxys4gmtd-userdebug && mka clobber && mka bacon
[Samsung Galaxy S (4G Model)] getochkn:
Got something that keeps freezes me at the welcome screen after installing gapps regardless of wifi or 3g.

EDIT. nm, did a fix permissions/davlink clear and signing into google now with my build.
[Samsung Galaxy S (4G Model)] Fluidification:
did you wipe data?

what rom are you coming from?
[Samsung Galaxy S (4G Model)] Fluidification:
I didn't really change anything until around 4:30ish.
[Samsung Galaxy S (4G Model)] Fluidification:
nevermind github is saying that I had some changes around 4 hrs ago, one of which broke something.
[Samsung Galaxy S (4G Model)] getochkn:
Well whenever I synced, it's working good so far. Thanks for the guide and the steps you took to put this together.
[Samsung Galaxy S (4G Model)] turtlepa:
Did you change the "build aokp" to "cm10.1"
[Samsung Galaxy S (4G Model)] Fluidification:
yes
[Samsung Galaxy S (4G Model)] turtlepa:
My build came out great. My first. I'm so happy. Thank you airfluip1!. No red border! hopefully i can get familiar with github more and help you with the gps if you let me...:laugh:

tom@tom-laptop:~/android/cm/out/target/product/galaxys4gmtd$ ls -la *.zip

-rw-r--r-- 2 tom tom 168168584 2013-06-22 13:52 cm-10.1-20130622-UNOFFICIAL-galaxys4gmtd.zip

-rw-r--r-- 2 tom tom 168168584 2013-06-22 13:52 cm_galaxys4gmtd-ota-eng.tom.zip

tom@tom-laptop:~/android/cm/out/target/product/galaxys4gmtd$
[Samsung Galaxy S (4G Model)] Fluidification:
I am building a new change right now.
[Samsung Galaxy S (4G Model)] FBis251:
Build, test. Build, test. Build, test. ONLY if it worked, push
[Samsung Galaxy S (4G Model)] Fluidification:
FB... you're really going to nag me about this aren't you...

I'm making branches specifically for debugging... one with libgps which already exists, and i'll make another for gpswrapper starting from my next change.

I promise I'll keep my base branch clean from now on!
[Samsung Galaxy S (4G Model)] cpkelley94:
I can no longer build your CM source. It gives me this error:

fatal: no <manifest> in /home/cpkelley94/android/cm/.repo/local_manifests/local_manifest.xml

EDIT: For some reason I had to directly copy in the local manifest, the curl was pulling in an HTML URL redirect instead of the XML file.

EDIT2: Sweet, repo synced in less than 2 hours ^.^
[Samsung Galaxy S (4G Model)] Theraze:
Same problem here. The local_mainfest failed to be "correct", but once the website was opened and the redirect followed, the redirected manifest synced fine. This applied to the following step:

curl https://raw.github.com/teamuserdebug/userdebug.github.io/manifests/manifests/cm10.1-aries.xml > .repo/local_manifests/local_manifest.xml
[Samsung Galaxy S (4G Model)] Fluidification:
are you guys CD'd into the correct dir?
[Samsung Galaxy S (4G Model)] Theraze:
Yep. In the ~/android/cm folder and it's putting in a local_manifest.xml file to .repo/local_manifests... that file is just telling it that it's redirecting though. Looks like git changed up the raw file location on you.

To clarify, I went to the same URL in Firefox, saved the page to local_manifest.xml (in ~/android/cm), ran mv local_manifest.xml .repo/local_manifests, and then the repo sync worked.
[Samsung Galaxy S (4G Model)] Fluidification:
huh?

Will look into.
[Samsung Galaxy S (4G Model)] Theraze:
Looks like the link you actually want there is https://raw.github.com/teamuserdebug/page/manifests/manifests/cm10.1-aries.xml instead. When I checked the curl page (https://raw.github.com/teamuserdebug/userdebug.github.io/manifests/manifests/cm10.1-aries.xml) that was the page it said it was redirecting to. When I saved that page instead, it actually gave me a working manifest.
[Samsung Galaxy S (4G Model)] turtlepa:
I havent had this problem
[Samsung Galaxy S (4G Model)] Fluidification:
because I updated the OP.

The error was that I changed a repo's name and forgot to update it here.

SO those who had init last week or yesterday had no problem.
[Samsung Galaxy S (4G Model)] Stuck on hold:
Regarding compiling on Windoze:

- download and install VirtualBox

- download an Ubuntu ISO

- start VB, create a new virtual machine using the wizard. Use the ISO file as install media.

- run Ubuntu and follow those instructions

Haven't installed a machine lately, nor compiled Android ever, but this should be close enough to get you going. I may try it later today, just for sgl's.
[Samsung Galaxy S (4G Model)] Fluidification:
The means to install Ubuntu isn't this guide's responsibility.

I am just stating that you can "natively" compile on mac and ubuntu.
[Samsung Galaxy S (4G Model)] Dwack:
Anyone else having trouble syncing?

dwack@dwack-DX4870:~/android/slimRoms$ mkdir -p .repo/local_manifests && curl https://raw.github.com/teamuserdebug/page/manifests/manifests/cm10.1-aries.xml > .repo/local_manifests/local_manifest.xml && repo sync
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 778 100 778 0 0 6356 0 --:--:-- --:--:-- --:--:-- 8189
fatal: remote error: Git repository not found
fatal: remote error: Git repository not found
fatal: remote error: Git repository not found
fatal: remote error: Git repository not found
fatal: remote error: Git repository not found
fatal: remote error: Git repository not found
fatal: remote error: Git repository not found
fatal: remote error: Git repository not found
error: Cannot fetch teamuserdebug/android_device_samsung_galaxys4gmtd_aries
fatal: remote error: Git repository not found
error: Cannot fetch CyanogenMod/android_hardware_samsung
error: Cannot fetch teamuserdebug/android_device_samsung_aries-common
error: Cannot fetch teamuserdebug/android_kernel_samsung_aries
fatal: remote error: Git repository not found
error: Cannot fetch CyanogenMod/android_packages_apps_SamsungServiceMode

error: Exited sync due to fetch errors
dwack@dwack-DX4870:~/android/slimRoms$
[Samsung Galaxy S (4G Model)] Theraze:
That usually means that there was either a hiccup on github, or that your firewall is blocking them. You're obviously downloading the repo file, since it knows which 5 repos fail. As such, all you need to do on that line, once you figure out why it's sad, is "repo sync" again. Start with hoping it's a problem that's going away on its own and just run the command a few more times after waiting a few minutes/hours and work out from there. :)
[Samsung Galaxy S (4G Model)] Dwack:
I can sync other repos though. I just got done doing SlimRoms git. It only pops up when I try to sync with that.
[Samsung Galaxy S (4G Model)] Tofuturtle:
Thank you! :D
[Galaxy S 4 Q&A, Help & Troubleshooting] azibux1:
I have found threads and info about how it works on the Note 2, about magnets in the stylus but how does it know when your finger is hovering over the S4 screen?

Anyone know?
[Galaxy S 4 Q&A, Help & Troubleshooting] MaKTaiL:
I have the same question.
[Galaxy S 4 Q&A, Help & Troubleshooting] damador:
Proximity sensor
[Galaxy S 4 Q&A, Help & Troubleshooting] azibux1:
The one at the top of the phone?

So it sort of senses downwards as well as infront of itself?
[Galaxy S 4 Q&A, Help & Troubleshooting] AndreiLux:
No.

It's the same old touchscreen controller technology just much more sensitive.
[Galaxy S 4 Q&A, Help & Troubleshooting] tomboymad:
I was reading about it's a new controller. With special features

Enviado desde mi GT-I9505 usando Tapatalk 2
[Galaxy S 4 Q&A, Help & Troubleshooting] rezaluchu:
I'm just curious.

What are stock apps that able to utilize this function. I only notice this when I use Flipboard.
[Galaxy S 4 Q&A, Help & Troubleshooting] Eambo:
I read somewhere that it was indeed the sensor at the top, mixed with the old technology too.

The apps I know it works with are stock email, stock texts and flipboard. Not sure what else. It doesn't even seem to work on lockscreen... :(
[Galaxy S 4 Q&A, Help & Troubleshooting] rezaluchu:
How to use the air view on Stock text? I thought it can show the contents of text from text overview display. But when I tried, nothing shown.
[Galaxy S 4 Q&A, Help & Troubleshooting] Thin_Bezel:
Sooo no way that this feature will be on the galaxy s3? Since it's hardware related
[Galaxy S 4 Q&A, Help & Troubleshooting] Fu5ion:
Samsung is using a super sensitive capacitative touchscreen that can sense your finger even when its a short distance from the screen, essentially. its the same reason that there's an option so that you can use it with gloves on
[Galaxy S 4 Q&A, Help & Troubleshooting] snapple232:
I'm no engineer, but this is my basic understanding gleaned from reading wikipedia and other sources. Capacitive touchscreens work by sensing changes in an electrostatic field. Your finger is an electrical conductor, which distorts the field. In normal phones the field is calibrated to extend just past the surface of the touchscreen. The S4's electrostatic field is simply overcalibrated to sense your finger from a distance, and it's also why it works with gloves on.
[Galaxy S 4 Q&A, Help & Troubleshooting] shadym1lkman:
delete
[Galaxy S 4 Q&A, Help & Troubleshooting] MiG123:
nothing to do with the capacitive screen or proximity sensor. if the screen was THAT sensitive it'll be firing off to even the slightest atmospheric disturbance. actual workings are related to the 2 IR sensors flanking the speaker grill which individually log IR intensities emitted by ur finger in front of the screen. an algorithm then compares these values and works out where ur finger is pointing.
[Galaxy S 4 Q&A, Help & Troubleshooting] ipsuvedi:
AFAIK it works with help of IR Sensor and/with Proximity Sensor

If screen sensitivity does this job then ...Nokia Lumia 920 to 520 all devices all should have this feature cuz all these devices have Super Sensitive screens

:)
[Galaxy S 4 Q&A, Help & Troubleshooting] GTRagnarok:
The air is much more inert than your finger. The proximity/IR sensors just blast IR beams away from the phone for things like Air Gestures and have nothing to do with Air View. They certainly don't shoot beams across the surface of the screen to detect your finger. The finger hovering simply uses a more sensitive capacitive touchscreen, as Sony explains here:

http://developer.sonymobile.com/knowledge-base/technologies/floating-touch/
[Galaxy S 4 Q&A, Help & Troubleshooting] Akhil:
This happened with me also.

The air view works in stock messaging app , gallery , flipboard and even when you dial a number if you have speed dial feeded.

For this you need to hold air view option in notification bar for about 2 seconds then a set of options will open. There you can switch on air view for messaging, gallery etc etc.

Sent from my Octa Core S4
[Galaxy S 4 Q&A, Help & Troubleshooting] Tomo1971:
It will be the electromagnetic field that the screen is detecting from your skin/finger. The same way that on other screens, they don't work with gloves unless you have the special gloves that have conductive fingertips on them.

Nothing to do with the sensors on the top of the phone cos if you cover them up, air view still works! Plus the sensors aim out the top and at 90 degrees to the phone face, how would they sense something almost touching the screen on the bottom?
[Galaxy S 4 Q&A, Help & Troubleshooting] Cloaker:
Works with the calendar also.
[Galaxy S 4 Q&A, Help & Troubleshooting] POLO_i780:
Stock Text

Stock Email

Flipboard

Gallery

Stock Video player (shows previews with sound, and on the progress bar)

Stock Music Player (Previews of song name and on progress bar)

Samsung Hub

S Planner

and S Memo

Just ensure you have Information Preview and Progress Preview turned On in Settings.
[One (M7) Accessories] r4dik4l:
https://www.youtube.com/watch?v=bTFwAxhpGVY

I made a video of this case. It is a very nice case, solid and keeps the phone safe.
[One (M7) Accessories] Droidguy987:
Very nice review
[One (M7) Accessories] _b_ship:
Awesome case, will eventually purchase.

Thanks for the review, I had no idea this case existed!
[Samsung Galaxy Nexus] Vihsadas:
Hey guys,

Long time lurker, ROM user since the Galaxy S days.

Weird, intractable bootloop problem here. Gets to boot animation sometimes gets to the "upgrading android" screen, then bootloops in a few seconds after upgrading a few apps. Usually bootloops during the boot animation (doesn't matter what ROM or Stock ROM I try). Ocassionally gets to my "SIM PIN" screen, then reboots before I have a chance to enter anything.

Normal State have Cyanogenmod and Franco Kernel running buttery smooth. (CM10.1M3 Snapshot + Franco 376 when problem started)

Problem Started When I tried to update CM to the new RC1 from the Cyanogenmod upgrade button in "settings". I had SuperSU installed overtop the built-in superuser. Everything was working fine.

What I have tried:

Have latest CWM: Have flashed, reflashed, wiped and re-wiped everything imaginable through CWM. All Caches, system sdcard, you name it, if it's an option in CWM I have tried formatting or wiping it and reflashing a ROM.

ROMs I have tried - CM10.1M3 Snapshot, CM10.1RC1 CM10.1RC2, ParanoidAndroid 3.5+ (Latest), Bigxie Maguro Latest.

Finally I got fed up and

decided to go back to STOCK, unrooted, unlocked

using fastboot.

I did:

> fastboot erase boot

> fastboot erase cache

> fastboot erase recovery

> fastboot erase system

> fastboot erase userdata

> fastboot flash bootloader magurobootloader.img

> fastboot reboot-bootloader

> fastboot flash radio radioxxlj1.img

> fastboot reboot-bootloader

> fastboot -w update image-maguro-jdq39.zip

And after booting back into the STOCK google recovery (man I haven't seen that screen in AGES) and resetting factory clearing cache. Low and behold -

STILL BOOT LOOPS!!!! What the hell!?!

I'm at my wits end. Any suggestions would be great. What am I forgetting here?!

I am absolutely desperate.
[Samsung Galaxy Nexus] bodh:
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
[Samsung Galaxy Nexus] Vihsadas:
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
[Samsung Galaxy Nexus] Vihsadas:
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.

Any other ideas?
[Samsung Galaxy Nexus] Vihsadas:
So decided to try TWRP just to see...well I dunno.

Interstingly enough when I got to hit "reboot" in TWRP it says "OS not installed!!" which is weird because I basically flashed the stock everything 4.2.2 (bootloader recovery, system, boot, everything) from fastboot. Then JUST flashed the TWRP recovery.

I really don't know what to make of this. I just tried keeping the battery out for like 2 minutes, then going back into fastboot and manually flashing:

bootloader

boot

radio

recovery

system

userdata

relocked bootloader

of the STOCK google maguro 4.2.2 (MD5 sum is good. It checked out)

And I still get a continuous reboot loop that doesn't even get past the "X" animation screen. Very ocassionally (1/10) it does get past that screen and I get to the screen where you choose your language, but right when I choose my language, the phone reboots and then continues the loop.

Honestly...Unless someone has another idea, I think I'm going to get another phone tomorrow and pray I'm under warranty. I hate to do it, because I've never had to do that before through all my flashing/ROM adventures...but I don't know what else to do. I've been using sideload for everything (except of course the fastboot flashing back to stock), but I doubt that has anything to do with it...I dunno crap.

anyone have any words of advice?
[Samsung Galaxy Nexus] Vihsadas:
One thing I thought i might work was redoing the partition table in Odin. So I tried this method:

http://xdaforums.com/showthread.php?t=2065470 (Thanks to Samersh72)

ODIN worked perfectly, download mode worked well, installed fine, and...

still bootloops!

Sometimes gets to "updating android" does a few apps, then bootloops. Once got to the screen where I select language, and before I could select anything - bootloop!

Do you guys think this is hardware? Right now I've installed stock 4.2.2 through ODIN and locked the bootloader in anticipation of returning the phone...
[Samsung Galaxy Nexus] samersh72:
give a try to omap flash

Good Luck
[Samsung Galaxy Nexus] Vihsadas:
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.

I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...

Do you think it's worth it to try?
[Samsung Galaxy Nexus] samersh72:
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
[Samsung Galaxy Nexus] Vihsadas:
Yeah you're right. OK done.
[Samsung Galaxy Nexus] beekay201:
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.

Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?

Sent from my Nexus
[Samsung Galaxy Nexus] Vihsadas:
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS? :(
[Samsung Galaxy Nexus] beekay201:
Yes, but There's a build.prop property that enables ADB debugging.. Since you have access to a custom recovery, you can mount /system rw and make your changes there.

Sent from my Nexus
[Samsung Galaxy Nexus] lsal25:
Similar issue

Hey guys,

I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
[Samsung Galaxy Nexus] mrgnex:
I dont know if you already did but try to wipe /system also and then flash a ROM.
[Transformer TF300T Q&A, Help & Troubleshooting] mihnea_gsm:
hello

I have an asus tf300tg and I did update to 4.2.1 JB. bootloader was unlocked before the update. Tablets started ok then I put TWRP 2.5.0 but it seemed like something was not working well because I could not see external sd card when I tried to give you wipe from TWRP, but said faild. I rebooted the tablet I entered fastboot and in this mode shows, three icons. RTK, android, and wipe again. And naturally I did wipe once, then never turned on.

Now bootloader is unlocked and starts straight into TWRP.

At first my pc (win7 64bit) Recognize that "transformes" then I searched and found "Naked drivers 0.72" in the idea of ​​connecting the tablet in fastboot and write something-anything but I DON'T HAVE SUCCES.

I installed in various ways (asus adb, google adb) of naked driver but I could not communicate via fastboot. Maybe I don't chose the right way

Does anyone else have a procedure that can be repaired?

And that since the corect connection mode that allows me to write on tablet via fastboot ?

I saw that the problem occurs in many places and forums (like here: http://www.teamw.in/project/twrp2/97 Note the comments) but I dont found a solutions.

BR

Mihnea

I wait with many interes your sugestions.
[Transformer TF300T Q&A, Help & Troubleshooting] JoinTheRealms:
Wrong forum, this needs to be in Q&A!

You need to find the 4.2.2 patched version of twrp and flash it via fastboot.
[Transformer TF300T Q&A, Help & Troubleshooting] mihnea_gsm:
Thx for answer.. OK I WIILL WAIT until apear 4.2.2.pached version of twrp.

BR

MIhnea
[Xperia Z Q&A, Help & Troubleshooting] Moody:
Hello,

First of all, allow me to indroduce myself. My name is Michael, and I have made some contributions to the XDA scene two years ago in the Xperia Mini Pro forums. I ported HTC Sense and Cyanogenmod 7 to that device and was the first to start the real development for that device.

With that said, I have retired for two years and have lost track of the developments. Anyway, on to my question:

Is it possible to port the HTC DNA / Butterfly J rom over to the Xperia Z?

Looking at the specifications, both devices feature a Qualcomm S4 Pro chipset, and a Adreno 320 GPU, empowering a screen with a resolution of 1080x1920 pixels.

Technically, this was the requirement to port a HTC Sense rom back in the days, a matching CPU, GPU and screen size. I do not know if this has changed.

My main reason for this question is that, if we can get the HTC DNA rom booting on the Xperia Z, we could also get the ported HTC One for the HTC DNA rom working on our phone, and enjoy Sense 5 (Minus Zoë)

I am looking forward to a reply from any skilled developer!
[Xperia Z Q&A, Help & Troubleshooting] Hellscythe:
this indeed looks very interesting

if i recall correctly sense has been ported to several devices like the gnex and S2

i wouldnt mind trying sense on my xperia z :3
[Xperia Z Q&A, Help & Troubleshooting] danw_oz:
Definitely sounds interesting, one big difference straight away are soft keys vs hard
[Xperia Z Q&A, Help & Troubleshooting] leminhnguyen0703:
Welcome back Mike. I was from Xperia Mini Pro forum as well and glad to see you back ! Are you intending to buy the XZ or do you already have it ?
[Xperia Z Q&A, Help & Troubleshooting] Moody:
Hey, good to see someone from the past :D

I already have the device, but porting is a pain in the you know what.

(Sense is not as easy to port anymore, + I have zero experience in kernel modifications.)
[Xperia Z Q&A, Help & Troubleshooting] mehmetolgungun:
Having sense would be great.

Hope you can do it.

I can help for tests if you want
[Xperia Z Q&A, Help & Troubleshooting] Hellscythe:
http://xdaforums.com/showthread.php?t=2245786

might help?
[Xperia Z Q&A, Help & Troubleshooting] Moody:
First of all, thanks for the thread. I have already tried a similar approach, but the problem is that HTC Sense 5 will not boot with these minor modifications to the kernel. I have to make more advanced customizations, of which I do not have the knowledge yet. I will try to contact the developer of the port for the Sony Xperia Arc, and it's fingers crossed that he'll be willing to help me out :)