Related
EDIT: EXTREMELY OUTDATED. I have not had this device for some time and will not be updating this post.
Please report all bugs encounter or search for and star the ones mentioned on these forums here: http://code.google.com/p/android/issues/list ; This is the official bug report forum of Google and the best way to let them know of the problems you are having. Don't post "Me too"s on known issues, simply star and cross your fingers!
Because people seem to be incapable of using the wonderful "Search" function built into these forums, I'm putting together a list of questions that keep popping up in new threads every other day.
Q: How's the Battery Life?
Officially, the Nexus S is rated for 6hrs of talk time and 427 of standby time. How much battery life you get will entirely depend on what you use the device for and how much. On my first real non-vacation day, my Nexus S lasted a little over 16hrs on one charge through what I would consider heavy usage (flashing roms/backups, emails, texting, web browsing, long phone calls, etc). Your mileage may vary. Fellow poster @Luxferro managed to get 2days, 14hrs, and 13minutes out of his phone on a single battery charge. Discussed here: http://forum.xda-developers.com/showthread.php?t=875809
Q: Does your GPS work?
Most people have reported their GPS to be functioning just fine, though there have been quite a bit of variation on lock times.
Q: Will this work on AT&T?
Yes, but you will not get 3G service. This is due to the different frequencies that T-Mobile and AT&T's 3G runs on.
Q: But it says it supports GSM band 850mhz!
GSM is 2G. UMTS is 3G.
Q: But Joe Bob/Dude down the street/My cousin's brother's nephew's wife said...
Stop it. It is likely that Google will release a version of the Nexus S with support for AT&T's 3G some months down the road, just like they did with the Nexus One but for right now, if you want 3G service, T-Mobile is the only way to go.
Q: Is tethering free?
So after having the phone for a bit of time now and tethering unimpended, I'm going to have to agree with @nxt that T-Mobile is not charging for or redirecting for tethering on this device. At least, for now. However, like in the original version of this answer, T-Mobile did announce that they were going to be charging for tethering but I've tethered every day for various amounts of time (including torrenting nearly a gig to my netbook) without so much as a hiccup. Source: http://bit.ly/d1NS9o
Q: Will TZones/Web2go/grandfathered web program work on this phone?
No, or at least, it doesn't appear to anymore due to T-Mobile locking down the IMEIs. When the phone was first released, people were reporting that it worked fine, then after a few days it became sporadic, before finally not functioning at all. See the discussion here for more information: http://forum.xda-developers.com/showthread.php?t=864843
Q: I unplugged my phone, and my battery dropped from 100% to 95% immediately, or it won't/takes along time to charge past 99%, what gives?
This is by design. Your phone will slow down and eventually stop pulling charge at or slightly greater than ~95% regardless of what your battery indicator says. This is to extend the overall life of the battery, as constant 100% to 0% charge/discharge cycles will cause it to fail prematurely. If you're interested in really pushing it to 100%, you can use a technique that is called "bump charging" and is better detailed here: http://bit.ly/f6xiZ0
Q: When I reboot my phone while it's charging, the battery jumps from X% to Y%, what gives?
I'm honestly not sure what causes this, but sometimes Android/Gingerbread gets confused on how much exact charge is in your battery if you reboot it while it's charging. However, from personal observation, it's just a display issue. Android/GB will eventually start showing the correct percentages once the battery has "caught up" with what it thinks it is at. Also wiping the battery stats(root only) seems to help alleviate this issue. Either way, it's not a large concern.
Q: Can we port SenseUI/Galaxy S apps to the Nexus S?
Most likely, no. Those apps typically require the Rosie/Touchwiz framework in order to function. You can have those apps when and if a developer decides to port those ROMs in their entirety.
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Follow the root guide stickied at the top of this forum: http://forum.xda-developers.com/showthread.php?t=895545
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Q: Linpack/Quadrant Scores?
Linpack doesn't play very nicely with the Galaxy S lineup generating very low numbers in comparison to HTC devices. This is because the processors that are powering these devices operate in different ways. Does this mean the Nexus S processors are slower? Not really, just different. As for Quadrant, it doesn't currently work very well with Gingerbread and needs to be updated. The scores folks have been seeing though put it in the 1600 range without a modified kernel.
Q: There's no LED Indicator? What are those two circles next to the speaker?
Correct, like all Samsung devices(minus the Epic 4G on Sprint) thus far, there is no LED indicator light. There are apps, such as NoLED, on the marketplace which work great on the Nexus S and provide more or less the same functionality. There's another app called BLN which will blink the capacitive touch keys to let you know you have a notification, but it requires a custom kernel to support it. Those two circles are the Proximity Sensor and Ambient Light sensor.
Q: I can't zoom in and out on the camera app!
Correct, the digital zoom feature seems to be missing.
Q: Can the Nexus S do 720p?
No, at least, not right now and not on the stock ROM. It is possible that eventually our wonderful developer community will come up with a software hack for custom ROMs to allow 720p video recording, but at a reduced framerate than if it had a true 720p chip similiar to what they did with the Nexus One. Until then, the answer is no.
Q: But that one guy in Italy says the Italian version can do 720p recording!
No, he says that it can do 720x480 which isn't the same thing. The 720p "name" comes from the last numbers in the resolution, so in this case, it would be 1280x720(which the other Galaxy S phones are rated to shoot at).
Q: How do I video chat?
Google, unfortunately, did not develop a native app to support video chat and so we must rely on some from the marketplace. Right now, as far as I'm aware, Tango is the only one that has been updated to support video chatting on the Nexus S.
Q: My toys are better than your toys! Hahahaha!
Stop it and grow up. Different strokes for different folks. People spend their money on what they want to spend it on regardless of your agreement on their choice. Not to mention that this kind of behavior goes against the spirit of this community.
Q: I'm rooted with Clockwork and can't install the OTA! I updated to 2.3.1 and lost root! What gives?
most of the time, official OTAs will not install through custom recoveries because of their tendency to break root or restore things like the stock recovery. Also if you've made any modifications to the system files such as replacing the default Mms.apk(messaging) with the custom Black Mms.apk found in the Themes & Apps section, or deleted any .odex files from the system partition, it will not install. The easiest way to update to 2.3.1 is to flash a custom rom such as one of the custom ROMs or use the 2.3.1 Stock NANDROID backup found in the development section. And yes, 2.3.1 "broke root." To regain it, simply follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=884499 (All credit goes to the original author(s) of the linked thread!). The aforementioned procedure is only needed on the Stock Nandroid Backup, not any of the custom ROMs.
Q: Clockworkmod says I'm not set up for OTAs! What gives?
That's not for official OTA updates from Google. Some custom ROM developers set up their roms to receive custom OTA updates or at least notifications of said update specifically for that ROM.
Q: Why have my Wifi/3G/Signal bars switched from green to white?
A green set of bars typically means that you are connected to and syncing with the Google Account servers. White means that this is not happening for whatever reason, usually something like a bad signal or low coverage area. Also the WiFi connection is set by default to turn itself off(aka sleep mode) when the screen is off, this can be adjusted under Settings > Wireless & Networks > Wi-Fi Settings > Menu Key > Advanced > Wi-Fi Sleep Policy. Don't panic, though, it's nothing too major.
(Suggested by mmas0n, thanks!)
Q: How do I restore the stock recovery?
Right now, it is NOT possible to flash the stock recovery over Clockwork Recovery at all. The only way to restore it is by NAND restoring the Stock 2.3.1 backup in the development section.
Q: Does the Nexus S have Gorilla Glass?
No, it does not. Take care of your device.
Q: The Nexus S only gets 3G? Omg, I only see a 3G icon!
The Nexus S gets UMTS and HSDPA, which are both technically 3G. Your phone idles on UMTS 3G, and when it starts downloading/uploading, it'll flip to HSDPA after a few moments. You can see this by typing *#*#4636#*#* into your Dialer, going to Phone Info, and looking at Network Type while downloading something. The ability to switch the icons on the notification bar is something that was added in custom ROMS, and is not supported by the stock ROM. Furthermore, the icon is not always an indicator of what kind of data connection you have. If I were so inclined(and I'm not) and/or had the technical skills(which I don't) to modify the framework, I could make it say OVER9000g when connected to anything. Rest assured, if you are on a network that uses the 3G bands the Nexus S supports, then you are recieving HSDPA regardless of what icon you see.
As suggested by Gogol(thanks!), now adding a...
Possible Known Issues(Reported by some users but not all):
Lag in the Web Browser
Back button is not responsive or doesn't light up
Pink / white / yellow tint on the screen
Weak WiFi signal
Weak cell signal (not necessarily specific to the Nexus S; T-Mobile's frequencies typically have bad building penetration)
Some apps running wild consuming battery
Missing apps in market (until Google updates to recognize 2.3.1 buildprint)
Accelerometer becomes "locked" after using Google Sky Maps requiring a reboot to free
Ringtones changing on their own following reboot/USB plugin (Push the .mp3 to /system/media/audio/ringtones to stop this *requires rooting*)
Stock launcher has home screen/scrolling lag issues (not present on market launchers like ADW/LauncherPro)
Home screen icons on stock launcher randomly disappear, disappear after move, or show up in folders they weren't moved to. (not present on market launchers like ADW/LauncherPro)
Please report all bugs encounter or search for and star the ones mentioned on these forums here: http://code.google.com/p/android/issues/list ; This is the official bug report forum of Google and the best way to let them know of the problems you are having. Don't post "Me too"s on known issues, simply star and cross your fingers!
EDIT: EXTREMELY OUTDATED. I have not had this device for some time and will not be updating this post.
Sti-cky! Sti-cky! Sti-cky!
Thanks for taking the time to make this list. Should be the first thing newbies read when they join the forum
Stuck due to the usefulness of this thread
Great FAQ thread man. Thanks a lot.
And lol @
But Joe Bob/Dude down the street/My cousin's brother's nephew's wife said...
Great FAQ, but it would be much better to add the list below, because there are many threads opened and will be more and more ...
Possible known issues:
1. Web browsing lag
2. Back button is not responsive
3. Cannot zoom when taking photo or video
4. Pink / white / yellow tint on the screen
....
Q: There's no LED Indicator? What are those two circles next to the speaker?
Correct, like all Samsung devices thus far, there is no LED indicator light.
Click to expand...
Click to collapse
Actually not true, the Galaxy S Epic 4G does have a LED notification light.
Q: Is tethering free?
No, tethering is not free. T-Mobile charges for this service. That being said, people have and still do tether without paying for the service with little to no consequence. T-Mobile seems to track the User Agent of the browser you're using on their network, and it is possible to mimic the Android browser's user agent on a desktop PC and tether undetected. In the event that T-Mobile discovers you tethering, you will receive a text message and all internet traffic on their network that doesn't contain the Android UA string will be redirected to an official T-Mobile site encouraging you to sign up for their tethering service.
Click to expand...
Click to collapse
This is wrong.
Tethering is free and included with the Nexus S as long as you have a normal data plan with T-Mobile (not any $5.99 or $10.00 T-Zone hacks/etc.). There is NOT an extra special $10 add-on tethering free.
jblparisi said:
Actually not true, the Galaxy S Epic 4G does have a LED notification light.
Click to expand...
Click to collapse
Thanks! This has been corrected.
nxt said:
This is wrong.
Tethering is free and included with the Nexus S as long as you have a normal data plan with T-Mobile (not any $5.99 or $10.00 T-Zone hacks/etc.). There is NOT an extra special $10 add-on tethering free.
Click to expand...
Click to collapse
Negative. As of 11/03, T-Mobile has begun charging for this service.
Source: http://www.tmonews.com/2010/10/t-mobile-launching-14-99-tethering-plan-november-3rd/
Android 2.2 introduced the ability to hotspot tether regardless of a paid service on nearly any device(and before that, this was available through some market apps). I believe some have had this ability "disabled," in the sense that it doesn't show up in the Wireless & Networks menu(such as the G2, though this was corrected in an update) but through apps such as AnyCut you can still activate the service and tether.
So, once more, you CAN tether without paying for it, however, T-Mobile may start redirecting your web traffic that doesn't contain the Android UA string to their website. They've been super inconsistent in their enforcement (a good thing, if you ask me!).
EDIT: After looking through the "services" options on my T-Mobile account, I don't see anything about a tethering plan. If other folks could take a peek and let me know, I'll revise that section and make the correction.
gogol said:
Great FAQ, but it would be much better to add the list below, because there are many threads opened and will be more and more ...
Possible known issues:
1. Web browsing lag
2. Back button is not responsive
3. Cannot zoom when taking photo or video
4. Pink / white / yellow tint on the screen
....
Click to expand...
Click to collapse
Thats a great idea, I'll definitely start try to start collecting known issues.
Understand that the development section for more detail on rooting / unrooting, but would greatly appreciate if you could post specific links in your FAQ to threads that you would use to root / unroot.
Am a newbie and since I see more than a couple of threads on the subject in the development section, I would greatly appreciate it if you can give links here based on your order of preference (after all its your thread) if there are more than one ways.
Point is a link in the FAQs would give more greater confidence
Paparasee said:
Understand that the development section for more detail on rooting / unrooting, but would greatly appreciate if you could post specific links in your FAQ to threads that you would use to root / unroot.
Am a newbie and since I see more than a couple of threads on the subject in the development section, I would greatly appreciate it if you can give links here based on your order of preference (after all its your thread) if there are more than one ways.
Point is a link in the FAQs would give more greater confidence
Click to expand...
Click to collapse
Updated to include links to two threads in the development section which should get you on your way.
The first one will help you setup ADB and the relevant drivers needed to input commands to the phone from your PC. The second is the actual rooting method and custom recovery installation.
unremarked said:
EDIT: After looking through the "services" options on my T-Mobile account, I don't see anything about a tethering plan. If other folks could take a peek and let me know, I'll revise that section and make the correction.
Click to expand...
Click to collapse
Again, since this is the Nexus S forum, the Nexus S, has NO tethering pay plans for T-Mobile. It's included and free. Yes that option was removed on the G2, etc., but again, this is the Nexus S.
nxt said:
Again, since this is the Nexus S forum, the Nexus S, has NO tethering pay plans for T-Mobile. It's included and free. Yes that option was removed on the G2, etc., but again, this is the Nexus S.
Click to expand...
Click to collapse
I'm well aware of which forum I am in and which phone I have.
The option was removed in the G2 and added back in via OTA update, it was also there on the MT4G at launch. I'll admit even setting my device to to show as one of those still does not pull up that option under services. I'm willing to believe that perhaps T-Mobile announced their intention to charge for the service then decided not to.
However, just to point out, the Nexus S/Nexus One are not special phones(as far as T-Mobile are concerned) on T-Mobile's network and thus entitled to special privileges. They are subject to the same rules and regulations as any other phone. In any which case, I'm going to make an adjustment to that section to note the ambiguity.
Is it just me or does the Nexus S seem to be more riddled with problems on release than most other phones? Perhaps it's just because of high expectations after the mind blowing release of the N1?
PhaedraCorruption said:
Is it just me or does the Nexus S seem to be more riddled with problems on release than most other phones? Perhaps it's just because of high expectations after the mind blowing release of the N1?
Click to expand...
Click to collapse
Not really. Every device has it's bugs and issues at release, the Nexus One included. Touch screen wigging out randomly, capacitive buttons misaligned, the relatively easy "death grip," and just generally (at least for me) weak 3G connection. My favorite was when the Nexus One wouldn't send or receive any text messages or phone calls.
We should also keep in mind that Gingerbread itself is brand new as well.
unremarked said:
Q: Can we port SenseUI/Galaxy S apps to the Nexus S?
Most likely, no. Those apps typically require the Rosie/Touchwiz framework in order to function. You can have those apps when and if a developer decides to port those ROMs in their entirety.
Click to expand...
Click to collapse
regarding this...
we might see some ports over in due time.
they guys over at SGS are already in the process of porting the SenseUI
once they are done with that feast, it'll be a lot more doable to bring it to Nexus S
http://forum.xda-developers.com/showthread.php?t=788866
and
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showthread.php?t=827745 Alpha ready for testing!
Please add "Q: Why do the Cell and WiFi signal icons switch to white?" or something to that effect.
We have 3 thread on this issue and I foresee many more.
mmas0n said:
Please add "Q: Why do the Cell and WiFi signal icons switch to white?" or something to that effect.
We have 3 thread on this issue and I foresee many more.
Click to expand...
Click to collapse
Done so! Thanks for the suggestion.
PhaedraCorruption said:
Is it just me or does the Nexus S seem to be more riddled with problems on release than most other phones? Perhaps it's just because of high expectations after the mind blowing release of the N1?
Click to expand...
Click to collapse
its just the high expectations, the NS wasnt a game changer like the N1 was
After the update I can't download anything from the marketplace. Anybody else have this problem?
katana24 said:
After the update I can't download anything from the marketplace. Anybody else have this problem?
Click to expand...
Click to collapse
Can't say that I have. Are you talking about missing apps, or are you getting some kind of error message?
I recently discovered that NOW when I use a mouse, up is down and left is right... Anyone else see this yet?
I know for a fact that it used to work just fine and was wondering if someone *may* know what may have caused this. Here are the facts so far:
Identical results with wireless usb, wired usb, Bluetooth, mouse by itself and one integrated with keyboard
Running Vegan5
Clemsyn's KERNEL
ChengLu's dataloop patch
SW2's Blue theme (older version)
Swype hack (edited build.prop)
Just wondering for those that are a little deeper into this where the code / source files / ect may be that might have gotten changed that could have caused this and if they is an easy way to get it back without a full wipe.
I have backup / restored but get the same result. Just looking for a few options before I start from scratch again.
Thanks for any insight.
it2steve said:
I recently discovered that NOW when I use a mouse, up is down and left is right... Anyone else see this yet?
I know for a fact that it used to work just fine and was wondering if someone *may* know what may have caused this. Here are the facts so far:
Identical results with wireless usb, wired usb, Bluetooth, mouse by itself and one integrated with keyboard
Running Vegan5
Clemsyn's KERNEL
ChengLu's dataloop patch
SW2's Blue theme (older version)
Swype hack (edited build.prop)
Just wondering for those that are a little deeper into this where the code / source files / ect may be that might have gotten changed that could have caused this and if they is an easy way to get it back without a full wipe.
I have backup / restored but get the same result. Just looking for a few options before I start from scratch again.
Thanks for any insight.
Click to expand...
Click to collapse
The first thing I would check is the kernel - reflash that (to stock, or a different one) and see if it works correctly. If that doesn't work let us know and we can try to dig deeper...
Does it do the same thing when you flip the tablet upside-down?
it2steve said:
I recently discovered that NOW when I use a mouse, up is down and left is right... Anyone else see this yet?
I know for a fact that it used to work just fine and was wondering if someone *may* know what may have caused this. Here are the facts so far:
Identical results with wireless usb, wired usb, Bluetooth, mouse by itself and one integrated with keyboard
Running Vegan5
Clemsyn's KERNEL
ChengLu's dataloop patch
SW2's Blue theme (older version)
Swype hack (edited build.prop)
Just wondering for those that are a little deeper into this where the code / source files / ect may be that might have gotten changed that could have caused this and if they is an easy way to get it back without a full wipe.
I have backup / restored but get the same result. Just looking for a few options before I start from scratch again.
Thanks for any insight.
Click to expand...
Click to collapse
I believe that this is due to the g-sensor fix that is included in Vegan. If you un-install that fix it will mess up your g-sensor but should fix the mouse 'issue'.
Makes sense.
I plugged a wireless usb mouse in last night and got basically the same results. Thought i had done something wrong, glad i searched and found this thread. Any chance someone could look at this please ?
Yeah, same here with Vegan beta 5.1
Don't want to mess up G se sorry because I have a lot of games that require it to work. But mouse being screwy is just as bad because I like to dock this thing and HDMI it to the 55 including flatscreen and use my Zippy keyboard/trackball combo to watch a movie or two now and then.
It is a "lose / lose" situation I think.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
My bluetooth mouse is working fine on tnt 4.1.0
Same Results here w/VEGAn5.1 using Wireless USB mouse.
Crossed signals?
Well... I'm glad to know it's not just me but sorry to hear we think it's the may be the g sensor fix.
If anyone has or can find an 'undo' for it I'd be willing to test. I dont use the tab for games but I need the mouse for rdp work.
Thanks for all the input do far!
...sent from my ' un-stock' vibrant
First post on the Vegan thread has the undo to regain mouse support: http://forum.xda-developers.com/showthread.php?t=884103
Here is a direct link to the patch to try: http://vegantab.gojimi.com/download/patch.VEGAn.BETA5.remove.Gsensor.zip
BigJohn
BigJohn89 said:
First post on the Vegan thread has the undo to regain mouse support: http://forum.xda-developers.com/showthread.php?t=884103
Here is a direct link to the patch to try: http://vegantab.gojimi.com/download/patch.VEGAn.BETA5.remove.Gsensor.zip
BigJohn
Click to expand...
Click to collapse
Thanks bigjohn... Worked perfectly!
Much appreciated.
swyped from my Vegan 'flavored' Gtab...
Well, since our old thread was locked, and since I'm continuing the development, the new thread is here. Many thanks to ajeet17181 for giving me the final piece of the puzzle to resume the work.
I am continuing ajeet17181's work on bringing a working Android build to our Windows Mobile phone, the LG Fathom. As of this moment I am only working on the Kernel, where most of the fixes need to be worked on, so let's get to it, shall we?
Download any of the following Android versions:
Gingerbread 2.3.7 (includes Kernel build #119)
DOWNLOAD "einsteinecker_android.rar" (thanks to pizzaboy192 for hosting)
alternate link (untested upload)
What works:
-3G data
-Wifi
-Limited Bluetooth functionality
-Video playback
-3D gaming
-Accelerometer
-Outgoing calls
What doesn't work:
-Camera
-Incoming calls
-SMS
-Vibrator
-Light sensor
-USB
-SD card has a low chance of being mounted.
-
Latest Cyanogenmod Nov 26, 2012
Cyanogenmod with working audio fix, updated link August 28 2013:
Part 1
Part 2
(split into 2 parts because my internet kept cutting it off)
Dead link
Thanks to www2287. Read this post for more info.
-
In some cases, the usual Google apps aren't built into the rom. Read this or this on how to get them.
-
Unsupported Android builds
ajeet's LG Fathom Gingerbread 2.3.7
Download here
What works:
-3G internet!
-Accelerometer!
-Wifi
-Real USB support.
-Outgoing calls
What doesn't work:
-D-pad is not aligned correctly.
-Cannot power off from shutdown menu.
-Incredible power drain. This is caused by the phone remaining at a high mhz without any way to fix it. Even if you use SetCPU to change the governor, the voltage looks like it remains the same so power drains even at 245mhz! :crying:
-No multimedia. And by that I mean no gaming for you, anything 3D is not even enabled on the kernel.
-No camera
-No SMS
-Cannot receive calls
-No light sensor
-No vibrator
Cyanogen Mod
Download here (link thanks to Giorgi-geo)
-
Cyanogen March 2012 build
Download here. from www2287. This build is not a final build, that means many things are broken in it.
-
Android 2.2 Froyo
Download here (NOTE: Due to Froyo not working in some areas, I will not provide support for it)
-
LATEST KERNEL: (March 14 2013)
ReRun March 13 2013: New compiling method to fix several bugs. Read this post for more info.
Previous Kernel:
Rerun kernel build #120
Rerun kernel build #119 (This kernel is a restart of my previous work. I basically started over from scratch and compiled it well over 100 times to find an acceptable solution to the battery issue.)
(Can't type the "." symbol? Download this.)
Kernel source:
https://github.com/ajeet17181/fathom-kernel Note: this source is broken, and since I have heavily modified it, wait for me to upload full source someday.
Booting Android-Now, to use it with one of the above Android versions, first extract the android version into your MicroSD card (You must have at least 750MB free space on your card), and then copy the 3 files inside the kernel archive into the Android folder, overwriting any older files. Next, open startup.txt and make sure the line "rel_path=fathom" has the name of the Android folder in your microSD card, if the folder is "2.2", change "fathom" to 2.2.
-Same as usual, run clrcad.exe about 5 times, then click on "haret" .exe file. The kernel will take a while to boot, so let it sit.
Preparing your phone to enable 3G internet on Android
Now that you have the ROM, you will need to edit your phone to enable 3G internet. Download this: http://www.mediafire.com/?azm89r85x6k2hhz (link thanks to da_reeseboy here.)
Please read the .txt inside the LGNPST archive on how to install. I can't help in that regard as I too funked my install until I undid everything and followed the txt file
After you set that up, download this: https://rapidshare.com/files/606560282/Clipboard01.zip, Or the the texty no frills way:
In windows mobile, change Fathom's USB mode to VZaccess manager mode. Open LGNPST and connect your Fathom. Go to "phone setting" and change default phone mode to GSM, and change the APN setting to the one your carrier uses.
I must warn that Android will attempt to connect when it boots, so be sure you have either an unlimited data plan or make sure you won't be charged if you use prepaid.
Current developments: Next phase of development will focus on the phone side (calls, sms, data). Because I am in a GSM country, I will be focusing on that.
Note: I am quite a busy person, and I won't be updating everyday, at the moment I have a grave matter to handle, and it is my 1TB hard drive. It has corrupt sectors, and it needs to be replaced. It holds crucial XDA data on it, so it is important to me. At the moment I can't afford a new one, so any donations is greatly appreciated in helping me remedy that problem. You can read more about my Hard Drive here.
Changelog
Latest Kernel:
March 14 2013
ReRun New Compile
This kernel was compiled differently than previous kernels, intended to join together the incompatible drivers with the rest of the drivers. This fixed several problems. Read here for more info.
-
November 23, 2012
ReRun kernel build 119
This kernel was restarted from the beginning, and slowly configured to the point where I found a solution to the "connect charger" error on boot. Basically, the kernel source had conflicting power settings combined from the HD2 and Tsunagi sources, and I simply removed the HD2 battery settings and provided a new working source code for the battery. I expect to use this as a base as I further eliminate the invalid .32 codes and replace it with .35 sources.
-
einstein 4x1 (NOTE: read any "readme.txt" files for instructions!!)
-Now, phone will no longer reboot when booting into android. You must make sure your battery level is over 26% in order to avoid this Reboot of Death bug, as it seems like the current build will reset if Android is in a mode where it will warn you to connect your charger. Perhaps we can change Android's low battery notification?
-NVRAM now pointed to /system/etc/wifi/, be sure to root copy the nvram.txt file into the new location.
-(for my modified Gingerbread build) attached are the correct key layouts for the Fathom hardware keyboard (thanks to www2287
Extreme Battery 003
-Re-started kernel development to ensure junk drivers were no longer included. This led to working Wifi, partial bluetooth, fully working headphone support, accelerometer, and as before, no immense power drain on standby. Overnight standby now a reality with Kernel 003!
Extreme Battery 002
Fixes:
-Wifi for Froyo, Bluetooth for Gingerbread
-Accelerometer works for Gingerbread only
-Headphones now work without fail
-Need more feedback regarding resetting while phone is on or off
Extreme Battery 001
Features:
-More CPU governors
-Overclock enabled (use at your own risk!)
-Extreme battery saving (need confirmation, my battery only dropped 2% overnight!)
Working:
-Main speaker
-Phone earpiece
-d-pad now aligned properly
-No more torn screen on the left side!
-Real power-down! Power button is the task manager button beside the camera button. Press this to turn your phone on or off.
Not working:
-Same as before, no outgoing SMS
-Wifi is dead :silly:
-Camera not working
-Never tried GPS...
-When headphones are plugged in, sound dies globally in Android.
Frequently Asked Questions
Where's my microSD card?
It seems strange, but this way worked for me: before you boot into Android, remove the sd card from your phone, then insert it, and then immediately boot into Android. If you did not do this when booting Android for the first time, do this method.
I'm low on storage space.
In "startup.txt", change "data_size=256" to "data_size=512" for 512MB of storage space. If you want more, change 512 to 1024 or 2048 for 1GB / 2GB respectively. Make sure you have that much free space on your MicroSD before you continue!
Can't start Froyo 2.2?
When you see the system process error, immediately press the side button beside the camera, then choose wait, then hold side button, then select power off, and the phone should look like it's booting again, and it should go into Froyo. If it doesn't, repeat again.
Can't boot into Gingerbread 2.3?
Due to a fault in ajeet's battery driver, the OS does not know what the battery life is at boot, and it thinks the battery is dead. Solution? Just make sure you have at least 70% or higher battery life when you boot into Android. I will try to focus on this, but as of the moment, I have not had much success in porting drivers into the kernel, as it is a rather complicated process and it has to be done in a way that will not break the wifi again. (This issue has been fixed in ReRun kernel build 119)
Reserved
Awesome that we have someone working on this again. Slightly curious how hard it would be to port this work over to OpenWebOS... But I'll love to see where Android goes. I'd try using it if the CDMA radio worked.
pizzaboy192 said:
Awesome that we have someone working on this again. Slightly curious how hard it would be to port this work over to OpenWebOS... But I'll love to see where Android goes. I'd try using it if the CDMA radio worked.
Click to expand...
Click to collapse
I'm optimistic CDMA would work, that unfortunately might need to have the Android OS edited to support dual mode CDMA/GSM. A nice place to start would be the Android builds for the Touch Pro2.
einsteinecker said:
I'm optimistic CDMA would work, that unfortunately might need to have the Android OS edited to support dual mode CDMA/GSM. A nice place to start would be the Android builds for the Touch Pro2.
Click to expand...
Click to collapse
We should also see what other Android-only devices used the same modems. The Droid series usually were world devices, as were a few others (none off the top of my head, but I bet they're pretty easy to find)
Worst case scenario would be to compile two different Android versions that are either CDMA only or GSM only.
I've got 3 Fathoms to test on, and would be more than willing to sell my unlocked one to someone who could use it better than I could (it's currently de-activated and I don't have a GSM SIM to test.
nice! thanks for your work einsteinecker
so here's my problem. i did everything as said. HTC logo comes on and that's it. i waited for 40+ minutes for it to load but nothing
edit: never mind. On the third try it loaded correctly
---------- Post added at 09:38 PM ---------- Previous post was at 09:00 PM ----------
-No more torn screen on the left side!
-Real power-down! Power button is the task manager button beside the camera button. Press this to turn your phone on or off.
Click to expand...
Click to collapse
love you. please fix wi-fi soon )
---------- Post added at 09:44 PM ---------- Previous post was at 09:38 PM ----------
i was using 2.3.1 android before this. now i installed 2.2 and the difference in performance is huge. 2.2 is much faster and smoother on our device. can you tell me what is the key difference between 2.3.1 and 2.2? if there is none I think it will be better to have 2.2
forget this too. looks like both build work better with your help )
Also. when in android, and i connect USB and transfer some files onto sdcard. they dont show up in file manager until reboot, and sometimes they just disappear. this is happening since first ajeet build - not a new problem, but maybe you could look into it.
---------- Post added at 02:47 AM ---------- Previous post was at 02:36 AM ----------
Not working:
-Same as before, no outgoing SMS
-Wifi is dead :silly:
-Camera not working
-Never tried GPS...
-When headphones are plugged in, sound dies globally in Android.
Click to expand...
Click to collapse
bluetooth also does not work )
Sorry folks, I meant to update yesterday but I had a mind crushing headache
pizzaboy192 said:
We should also see what other Android-only devices used the same modems. The Droid series usually were world devices, as were a few others (none off the top of my head, but I bet they're pretty easy to find)
Worst case scenario would be to compile two different Android versions that are either CDMA only or GSM only.
Click to expand...
Click to collapse
I recall most Droids from Motorola have the OMAP cpu, so I'm not sure if using the code for that would work on our Qualcomm stuff (I believe LG used a Qualcomm reference guide for the Fathom). I figured checking Qualcomm's sources first is a good try.
I've got 3 Fathoms to test on, and would be more than willing to sell my unlocked one to someone who could use it better than I could (it's currently de-activated and I don't have a GSM SIM to test.
Click to expand...
Click to collapse
I've been interested in something. How is android on the newer updates? What I mean is that, I'm still running stock V4 Windows Mobile ROM on my Fathom, and there is no performance lock like on the HTC HD2 (full 1Ghz on battery). Does the V5 or V7 WM Roms have this too?
Giorgi-geo said:
i was using 2.3.1 android before this. now i installed 2.2 and the difference in performance is huge. 2.2 is much faster and smoother on our device. can you tell me what is the key difference between 2.3.1 and 2.2? if there is none I think it will be better to have 2.2
forget this too. looks like both build work better with your help )
Click to expand...
Click to collapse
One main difference I see between 2.2 and 2.3, is that 2.3 rotates the screen immediately after you slide out the keyboard. 2.2 will only rotate once you open a program.
Giorgi-geo said:
Also. when in android, and i connect USB and transfer some files onto sdcard. they dont show up in file manager until reboot, and sometimes they just disappear. this is happening since first ajeet build - not a new problem, but maybe you could look into it.
Click to expand...
Click to collapse
If you read the readme text file inside the 2.2 Android build, you'll see it's a problem of the OS:
"- USB Mass Storage (You can copy files from PC to PC. But Android apps cannot see the copied files in the phone before rebooting.)"
I think that is because we run Android from our SD card.
bluetooth also does not work )
Click to expand...
Click to collapse
Thanks for the feedback. I was going to upload the headphone fix yesterday, but maybe I'll try that bluetooth fix too.
einsteinecker said:
I recall most Droids from Motorola have the OMAP cpu, so I'm not sure if using the code for that would work on our Qualcomm stuff (I believe LG used a Qualcomm reference guide for the Fathom). I figured checking Qualcomm's sources first is a good try.
I've been interested in something. How is android on the newer updates? What I mean is that, I'm still running stock V4 Windows Mobile ROM on my Fathom, and there is no performance lock like on the HTC HD2 (full 1Ghz on battery). Does the V5 or V7 WM Roms have this too?
Click to expand...
Click to collapse
I am not sure what the differences between the OMAP refrence and the Qualcomm refrence designs are. I know the Fathom is a 1ghz Snapdragon, but not sure what else it has in it.
Also, what do you mean by performance lock? I run my own ROM (V6) and it seems to run well. I don't do OC, but I have successfully underclocked the device to 215mhz (somewhere around there) as a test and it was stable. Eeked almost two weeks of battery out of a test device that way.
maybe you could fix wi-fi too? it was working before, so if you could compare the code you could probably fix it fast.
---------- Post added at 12:42 PM ---------- Previous post was at 12:19 PM ----------
one more thing. in android it only shows 165mb ram
---------- Post added at 12:54 PM ---------- Previous post was at 12:42 PM ----------
IMPORTANT: when going back to Windows Mobile, do not, I repeat DO NOT reset the phone while Android is off (screen off, standby). Make sure Android is on before you go back into Windows Mobile, if you don't, Android will be locked into an eternal "off" state, and you will never be able to go back into Android again.
Click to expand...
Click to collapse
I think this just happened to me. every time i load android it goes to unlock screen and then turns off. i always turned android off from its own menu so i dont know why it happened. there has to be a way to fix this, help please?
---------- Post added at 01:46 PM ---------- Previous post was at 12:54 PM ----------
after 5 tries, i connected phone with charger and on the second try it turned on
Hi folks, after my previous build work for headphones and not Bluetooth, I tried fixing Bluetooth but now the headphone port is wonky :silly:
While that was happening, I found out why Wifi wasn't working. Now, on 2.3 Gingerbread Wifi doesn't work (probably firmware problem), but in 2.2 Froyo it does work, but can't find any networks
That's when I was trying to fix things on the Android side (not the kernel) when I apparently got one thing to partially work:
I hope you noticed the 3G icon on the top, yes it's very close to working, the only problem I've got is making the phone realize that there is a sim in there (and the outgoing number to dial). Now, 2.3 Gingerbread can see the sim, so I'm going to try that, but if this works, I think we're in for a heck of a ride
Once I have both headphone and Bluetooth support stabilized, I will upload that. The 3G and Wifi fixes involve the Android OS itself, so that means I have to uploaded the OS or give instructions how to patch them in yourself.
pizzaboy192 said:
I am not sure what the differences between the OMAP refrence and the Qualcomm refrence designs are. I know the Fathom is a 1ghz Snapdragon, but not sure what else it has in it.
Click to expand...
Click to collapse
Well I certainly won't rule anything out. Right now any thing is a good thing to test, who knows, maybe the Droid actually has what I'm looking for
Also, what do you mean by performance lock? I run my own ROM (V6) and it seems to run well. I don't do OC, but I have successfully underclocked the device to 215mhz (somewhere around there) as a test and it was stable. Eeked almost two weeks of battery out of a test device that way.
Click to expand...
Click to collapse
Performance lock is like this: when I had the HD2, while on battery (no AC plugged in) the phone will have only a maximum speed of 768Mhz. My Fathom does not have this, it is a max 1Ghz on battery and on AC. What I'm wondering is, maybe LG's V5/V6/V7 updates changed something, I'm not sure. I sure don't want to risk my only phone either, and there's more: what if all this time LG's updates also updated the phone baseband. So while I'm porting Android to our phones, maybe my updates won't work with the old V4 I'm running. There certainly is a lot of things to consider when doing this stuff :silly:
Giorgi-geo said:
I think this just happened to me. every time i load android it goes to unlock screen and then turns off. i always turned android off from its own menu so i dont know why it happened. there has to be a way to fix this, help please?
Click to expand...
Click to collapse
I think there might be a way to fix this, unfortunately I have had little succes porting drivers over to my kernel. It is one of the reasons why I can't get the camera to work yet, porting drivers is not as simple as copying and pasting drivers like in windows mobile.
But I think it could work, you see, my idea was to tell Android that there's a reset button onboard the phone (the one beside the charging port). LG has the code for this, which I was able to see, but haven't been able to get working yet.
Edit: Wifi is still dead on 2.3 Gingerbread, but I fixed the Accelerometer :victory:
Couldn't test Froyo because I broke the Android build, will redo and continue further tests
Awesome work! I'll run some tests on my end with the CDMA half if you'd like and report back to see what is and isn't working connectivity wise there.
As for the WiFi half: is it getting an IP address? Can you check the DNS settings to make sure they are being set properly?
As for the performance lock: none that I know of.
And as for the question about baseband: No baseband differences between ROM versions. They're purely a WinMO flash, and not a BaseBand flash. If you'd like, I can run tests on all 3 OEM versions of the ROM though, as I have 3 unused Fathoms, all on different ROM versions currently. I've even tried cooking a WinMo ROM that autoboots into Android (almost works, tempted to just put a HaRET shortcut in startup and strip out all WinMO core programs.
Froyo doesn't like my kernel anymore, even tried a different SD card and it still has a system crash on boot. I guess it's time to work on a new OS :crying:
pizzaboy192 said:
As for the WiFi half: is it getting an IP address? Can you check the DNS settings to make sure they are being set properly?
Click to expand...
Click to collapse
It's just scanning, it won't even find the network
And as for the question about baseband: No baseband differences between ROM versions. They're purely a WinMO flash, and not a BaseBand flash. If you'd like, I can run tests on all 3 OEM versions of the ROM though, as I have 3 unused Fathoms, all on different ROM versions currently. I've even tried cooking a WinMo ROM that autoboots into Android (almost works, tempted to just put a HaRET shortcut in startup and strip out all WinMO core programs.
Click to expand...
Click to collapse
Oh, that's what I wanted to know, if the LG updates include a radio update. I'm highly interested in knowing if there will be better performance in Android if they updated the radio.
einsteinecker said:
Oh, that's what I wanted to know, if the LG updates include a radio update. I'm highly interested in knowing if there will be better performance in Android if they updated the radio.
Click to expand...
Click to collapse
We could also see what other devices used the same radio chip. I know that plenty of them are out there, it's just a matter of finding one that will provide an updated baseband and see how badly it screws up the phone (since we don't have the OEM baseband, doing that would probably brick any device you modded, if it went wrong)
How are you doing your work? any possibility of throwing it on some place like github so that people like me can try out changes and put our own in to help out? I have a test fleet just sitting doing nothing since I can't get much more out of Windows Mobile and cooking ROMs has gotten rather repetitive.
pizzaboy192 said:
We could also see what other devices used the same radio chip. I know that plenty of them are out there, it's just a matter of finding one that will provide an updated baseband and see how badly it screws up the phone (since we don't have the OEM baseband, doing that would probably brick any device you modded, if it went wrong)
How are you doing your work? any possibility of throwing it on some place like github so that people like me can try out changes and put our own in to help out? I have a test fleet just sitting doing nothing since I can't get much more out of Windows Mobile and cooking ROMs has gotten rather repetitive.
Click to expand...
Click to collapse
The kernel source is in the first post That's all I'm doing now, I get discouraged when I see the steps I have to take to make the Android OS, neither ajeet or www27 uploaded that and it's going to be a lot to download (I have limited bandwidth) What I've been doing is modifying Android while it's running (root access), and that's how I applied the accelerometer and that 3G thing.
Tomorrow I will upload the latest fix, which includes:
-bluetooth support (paired with headset and able to receive files)
-headphone support fixed
-how-to for the accelerometer (I will add a game so you can test it )
I'm currently prioritizing 3 things: why the SD card doesn't always mount on boot, charging the phone while using Android, and why my kernel doesn't like Froyo and the fixes that used to work.
einsteinecker said:
I'm currently prioritizing 3 things: why the SD card doesn't always mount on boot, charging the phone while using Android, and why my kernel doesn't like Froyo and the fixes that used to work.
Click to expand...
Click to collapse
what's wrong with charging? i dont see any problems
Random question: any way to get the Android main to boot off the internal flash? if so, I could build "ROMs" that boot WinMo and immediately start HaRET and handoff to Android. I tried earlier, but ended up with a failed boot every time.
This mod is not developed / maintained anymore.
The mod is based on an (now) old version of the Pioneer AppRadio app that does not support the latest Android versions and head units.
If it works then it works but if not then you are on your own. There is no support. Also the ARUnchained GPS Injector app is not developed anymore.
To use AppRadio Unchained please get the paid version from the Play store called ''AppRadio Unchained Reloaded".
For details see here: AppRadio Unchained Reloaded
If you don't want to root your phone and have Android 7 or higher there's AppRadio Unchained Rootless
Old information:
=================================================================================================
The Pioneer AppRadio is a radio with a 7" touch screen. Android devices can be connected via HDMI and shown on the screen.
Touches and keypresses are sent back to the Android device via Bluetooth. The radio has a GPS receiver and data is sent
over Bluetooth as well. In essence a very nice concept.
To connect to an AppRadio there's a Pioneer AppRadio app available in the Play store. The Pioneer AppRadio app
is however quite restrictive. It allows only to run a small number of apps that are approved by Pioneer. These approved
apps can interact with the AppRadio app because they have a built in Pioneer SDK. The number of useful apps is small.
For details look here: Pioneer Appradio Knows website.
The goal of this project is to modify the Pioneer AppRadio app in such a way that it allows full mirroring.
This means that any app can be used and controlled using the touch screen and keys on the headunit.
Also any application can receive GPS data from the AppRadio.
Setup guides by RogerH
Pioneer AppRadio with Nexus 5
Setting up Pioneer AppRadio with Android Stick
Links
CNET article that gives a nice overview
Video from Steven Solazzo
Video from SinisterC6
Video from Neil Fontamillas
Video from M Sylvester showing AVH-4000NEX working
Video from M Sylvester showing AVH-8000NEX working
Video from M Sylvester showing Samsung Note 3 hardware setup
Video from Pascal H showing ARU in action in a Porsche 997 Turbo (in French)
Current status of the AppRadio Unchained Mod (free)
Beta release 6 is available for testing.
You can download it from here: arunchained0.16.apk
For Android HDMI sticks there's a special version available.
You can download it from here: arunchained0.15stick.apk
Current status of AppRadio Unchained Reloaded (has built in GPS Injector) (paid)
In addition to the AppRadio Unchained mod of the Pioneer AppRadio app, a completely Pioneer-less app was developed.
Basically it allows you to connect to your AppRadio in a faster and easier way without the need to use Tasker.
For details see here: AppRadio Unchained Reloaded
Current status of the ARUnchained GPS Injector (to be used with the AppRadio Unchained Mod) (paid)
GPS injection on system level using mock locations is available in the playstore here: ARUnchained GPS Injector
For GPS Injector details go to the FAQ here: ARU FAQ
Please fill out the survey here: ARUnchained GPS Injector survey
Navigation apps that already have AppRadio support like Waze and Navfree still work using the HU GPS. If you only use those apps then you don't need ARUnchained GPS Injector.
Head unit models that have built in navigation like AVIC-Z150BH, AVIC-F50BT and similar are not supported as Pioneer does not support sending of GPS data to the android device. If you are unsure, a test that can be done is to install Waze, if Waze can use the GPS of the head unit, ARUnchained GPS Injector works as well.
Release notes beta release 6
Rotation locker only active when HDMI connected.
ARU menu also available when not connected from Settings / Help menu.
Rotation locker and Start GPS Injector are now separate options.
Release notes beta release 5
Right part of the screen not reachable on Nexus 5 issue fixed.
Touch made more accurate for all phones.
Release notes beta release 4
Start / stop GPS Injector service when bt connected / disconnected.
SWC extended with ff & rw (to be tested by M.a.s.e-> doesn't work)
Play/Pause of HU quick menu bar now working.
Release notes pre-beta release 3
Steering wheel controls are working now.
For details go here: ARU FAQ
Release notes pre-beta release 2
Multitouch implemented.
Hardware keyboard issue fixed.
Options menu available.
Rotation locker.
Invert XY-coordinates. -> Does not work 100% yet.
Release notes pre-beta release 1
Radio buttons are working now.
Alternate method for setting uinput access rights fixed.
Release notes pre-beta release 0
Root access is required so your phone must be rooted.
For now it only allows using the touch screen.
Only single touch is supported.
Keys from the radio don't work yet.
GPS from the radio doesn't work yet.
Steering wheel controls don't work yet.
Users have reported it working on AppRadio 2, AppRadio 3, AVIC-F950, AVH-X8500BHS and AVH-X8550BT.
Disclaimer: Use at your own risk. Basically if it damages anything (you / your phone / your radio / your car or whatever),
don't blame me.
Donating
If you like my work and want to donate something, click on the "DONATE TO ME" button. However the first page will show in Dutch ( I guess because I am registered there).
Two solutions:
1) In another browser window logon to Paypal first. Then press the "DONATE TO ME" button here.
2) At "Donatiebedrag" enter the amount in US$ you want to donate, at "LOG IN OP PAYPAL" enter your logon details. After logon the language will change to your local language.
FAQ
For FAQ go here: ARU FAQ
Common issues and solutions
For an overview of common issues go here: Common issues and solutions compiled by stewbuntu
For help on what hardware to use you can also go here: Appradio forums It's basically the ARLiberator forum but has information about how to setup your hardware too.
Compatibility list
This app is compatible with any AppRadio that is supported by the original AppRadio app.
Details of supported Android devices:
Please fill out the survey here: ARUnchained survey
You can also report the issues that you have.
See attached ARUnchainedSurvey03.zip file for results of the survey. It's a zipped pdf file (had to zip it because of pdf size limitation on XDA). It gives a good overview of what phones/radios are working with ARU.
Old releases
Beta release 5 is still available in case 6 doesn't make you happy: arunchained0.15.apk
Beta release 4 is still available in case 5 doesn't make you happy: arunchained0.14.apk
Pre-beta release 3 is still available in case 4 doesn't make you happy: arunchained0.13.apk
Nice work! I can't wait to get home and test it out.
In the other thread I saw that someone had a S4 working with the AR3 using your app, so you have me really tempted to upgrade from the AR2 If you get GPS working on the AR3 you can definitely count on a donation from me.
FAQ
ARUnchained GPS Injector
The ARUnchained GPS Injector app has two parts inside. One is the GPS service and one is the UI activity.
The service is the part that injects the GPS data into mock locations. ARU 0.14 and up will start this service automatically when a bluetooth connection is made to the HU (at the same moment that the rotation locker is started). The GPS service is stopped when bluetooth is disconnected.
The UI activity is started when you start the ARUnchained GPS Injector app from the launcher. It shows the status of the GPS service and also the actual GPS data. The purpose is to be able to check whether the service is working properly. With the start / stop buttons the GPS service can manually be started / stopped.
For the GPS service to work Mock locations has to be enabled. To use the phone built in GPS, Mock locations has to be disabled. It can become tedious to set this manually so ARUnchained GPS Injector has an auto on/off Mock locations feature. In order for this to work ARUnchained GPS Injector has to be converted into a system app.
This involves moving "mars.area51.arunchainedgps.apk" from "/data/app" to "/system/app". This can be done with root explorer for instance. Set permission to rw-r--r-- and reboot your phone. On Android 4.4 (KitKat) you should move the apk to "/system/priv-app" folder instead.
For pre-KitKat Android versions converting to system app can be done using Titanium backup:
Open Titanium Backup
Search for ARUnchained GPS Injector
Long press and choose convert to system app
Reboot phone.
Converting to system app using free ES File Explorer
1. Make sure in ES File Explorer, Root Explorer is enabled and Mount R/W is on RW
2. Copy pkg.apk in /mnt/asec/mars.area51.arunchainedgps-1 to SDCard and rename it 'mars.area51.arunchainedgps-1.apk'
3. Install 'mars.area51.arunchainedgps-1.apk' from SDCard
4. Move 'mars.area51.arunchainedgps-1.apk' from 'data/app' to /system/app or /system/priv-app on 4.4.x
5. In /system/app or /system/priv-app select 'mars.area51.arunchainedgps-1.apk' and in menu select Install.
6. After install reboot
How to make a logcat using an app called Catlog
Start Catlog logcat through app menu and select record.
Select home button so you leave Catlog app running.
Go through process to start ARU and connect to AR.
Once you know the bug was created, open the Catlog app from notification bar (this stops recording).
Select the recording, which is named by date-timestamp...from action selection pick share by email...this zips the logcat and system info txt files into one zip.
Email to self and share the zip with dev by email or any other method you want.
On my Samsung phone not the whole screen is shown but a part is cut off
A) The default Samsung launcher doesn't handle landscape well. The solution is to install an alternative like Nova launcher.
On my Samsung phone touch stops working after calibration
A) Verify your phone is rooted properly.
B) On Android version 4.3 and higher Samsung has Knox security and SELinux is in enforcing mode.
This somehow prohibits accessing the /dev/uinput device which is required to be able to input touch/key events on system level.
In order for ARU to work Knox has to be disbled and SELinux has to be in permissive mode.
Possible fix 1:
First install an app called Android Terminal Emulator then open a terminal and type
the following lines pressing enter after each line:
su
pm disable com.sec.knox.seandroid
Now wait a bit till knox is killed and finally type:
setenforce 0
If this works, you have to do it every time you reboot your phone. It can be automated with Tasker for instance
Possible Fix 2:
Install the Xposed framework and the Wanam module.
At Security hacks tick " Disable Knox notifications" and "Disable SEandroid".
Reboot.
Possible Fix 3:
If the other fixes don't work and your bootloader isn't locked you can try to install a custom kernel that has Knox disabled and SELinux in permissive mode by default.
Keyboard use
It's not necessary to install Car Keyboard. Only the original Pioneer AppRadio app needs that.
Note that the virtual keyboard created by ARU is sometimes incorrectly detected as a hardware keyboard.
This prevents the software keyboard to be shown and makes it impossible to enter anything.
To check / set the keyboard settings:
Click the menu button on ARU.
At the right bottom click on "Change input method"
A pop-up is shown that CarKeyBoard has to be installed. Ignore it by clicking OK.
The dialog for selecting the input method is shown.
Make sure hardware keyboard is switched off.
Use of the hardware buttons:
The home, menu and back button now work as advertised.
To go back to the native interface you have to open the AppRadio app manually and then press the home button.
To go to the AppRadio app easily, swipe down the status bar and click the AppRadio notification.
Fast option to go back to the native interface: Double click the home button, touch the blue bar in the middle with 4 squares on the left.
Release notes pre-beta release 2
Multitouch implemented.
Multitouch works now. AppRadio 3 has a bug which makes it a bit unpredictable.
Hardware keyboard issue fixed.
Sometimes the virtual keyboard created by ARU was incorrectly detected as a
hardware keyboard preventing the software keyboard to be shown. Fixed now.
Options menu available.
The options menu can be reached from the app's main screen. There's now an additional ARU
option sub menu available with two options:
Rotation locker.
Invert XY coordinates.
When in AppRadio Mode homescreen, select menu button, select ARU, there you will see the ARU feature options...only accessible when connected to HU at this time.
Options can be set but will only become active after force stopping the app and then restarting it.
Go to Settings->Apps->AppRadio Unchained and do a Force stop. After that just start ARU again
and the options will take effect.
Rotation locker.
Forces rotation to be in landscape when enabled.
Locker becomes active when a bluetooth connection is established with the radio.
Locker is deactivated when bluetooth is disconnected.
Invert XY-coordinates.
Necessary for some tablets and HDMI sticks.
Currently this options doesn't work well. Somehow it will switch mode during calibration, giving
incorrect calibration results. After that touches are at the wrong position meaning app is useless.
Will look into it soon.
Release notes pre-beta release 3
Steering wheel controls
Steering wheel controls are working now.
Currently supported are: previous track and next track.
There might be more but I couldn't get it out of my radio.
Of course there's volume, mute etc. but that is handled directly by the radio
and never sent to the phone.
In case there are commands sent by the radio to the phone besides the ones already implemented the logcat will contain this:
Don't know how to translate RemoteCtrlInfo = <number>. Let me know the number and what remote control command you were
issuing and I can add it.
Hell yeah man! Thank you! will test soon on my AR3. If you have that bitcoin address set up I'll send you like $20 worth of btc for this mod.
great... waiting so long for getting AR3 support...
will test it today and donate as well...
Gesendet von meinem Nexus 7 mit Tapatalk 4
Original Hack Bounty Crew:
--------------------------------------------------------------------------------------------
$200 lpasq (xda) Confirmation number: 7D019513V95549722
$100 drawblood (appradioforum & xda) Donation made per post on AppradioForum
$50 ofarrell.g1 (xda)
$50 evillela2001 (xda) Confirmation number: 3NF91232VR227492L
$50 Meldoon (xda)
$25 rs2k (xda) Confirmation number: 8R358541KC016842T
$25 jj69chev (xda)
$25 leobg (xda) Confirmation number: 8TE693651C300254U
$25 tnuts22 (xda) Paid
--------------------------------------------------------------------------------------------
$550 Committed - U.S. Dollars
($425) Confirmed Donated
==============================================
$125 Due
hey Area51. i have a bugreport for u. appradio app from market work ok on lg p999 with stock 2.3.4 fw, but modified app crash twice at startup. then it work seems fine(cant test it with pioneer now). on same phone with cm7(2.3.7) and cm10 all ok. i have a log dump for u: http://pastebin.ca/2455597
Alright just got done testing with my note 1 I717 running stock 4.1.2. Couldn't get it to work at all. Bluetooth is connected as I can stream google play and make phone calls through the unit. However, when I connect the MHL adapter to the deck, I get an icon that I can only describe as a map with a speech bubble with a bluetooth symbol in it with an x by it. I'm assuming it means no bluetooth connection. However streaming music via bluetooth is currently going on. Now on the phone side, normally in the non modified version of ar before the mhl adapter is plugged in and bluetooth is connected, it gives a picture of a usb cable on the phone with an arrow saying plug in. On the arunchained, it just gives the Bluetooth symbol with 6 dots like it's not connected. I'm terrible at bug reports so if you have any questions I'll try to answer it.
Your phone has to be rooted for this app to work
tmp_do said:
hey Area51. i have a bugreport for u. appradio app from market work ok on lg p999 with stock 2.3.4 fw, but modified app crash twice at startup. then it work seems fine(cant test it with pioneer now). on same phone with cm7(2.3.7) and cm10 all ok. i have a log dump for u: http://pastebin.ca/2455597
Click to expand...
Click to collapse
I think it may be due to code obfuscation stripping a bit too much code. Thanks for the report.
Droid Bionic
I donated 50usd...even without the AR2 hardware buttons working, this app is awsome. I use an old rootrd stock Droid Bionic, and your app works perfect for me. No lag, no parts of the screen I can't get to, just works perfect. Thanks for all the hard work, buy some drinks on me.
gbual said:
Your phone has to be rooted for this app to work
Click to expand...
Click to collapse
It is rooted.
jdbaldi said:
I donated 50usd...even without the AR2 hardware buttons working, this app is awsome. I use an old rootrd stock Droid Bionic, and your app works perfect for me. No lag, no parts of the screen I can't get to, just works perfect. Thanks for all the hard work, buy some drinks on me.
Click to expand...
Click to collapse
Don't pay me too early, the app is not even finished. I might take the money and run......
J/k, I will finish everything.
And I have to add, thanks a lot for the donation!
Area51© said:
Compatability list
To be done.
Click to expand...
Click to collapse
Try this https://docs.google.com/forms/d/1sz8ItL_d4NlLWP33-JK1aaxv8-LWZGuKPjr1RuMNlBI/edit?usp=sharing
Area51...paste link to OP if it works for you.
enjoimadcow said:
Alright just got done testing with my note 1 I717 running stock 4.1.2. Couldn't get it to work at all. Bluetooth is connected as I can stream google play and make phone calls through the unit. However, when I connect the MHL adapter to the deck, I get an icon that I can only describe as a map with a speech bubble with a bluetooth symbol in it with an x by it. I'm assuming it means no bluetooth connection. However streaming music via bluetooth is currently going on. Now on the phone side, normally in the non modified version of ar before the mhl adapter is plugged in and bluetooth is connected, it gives a picture of a usb cable on the phone with an arrow saying plug in. On the arunchained, it just gives the Bluetooth symbol with 6 dots like it's not connected. I'm terrible at bug reports so if you have any questions I'll try to answer it.
Click to expand...
Click to collapse
Hmmm, basically that part (Bluetooth communication etc.) is not changed from the original app. So I don't really understand why there is a difference. It seems you are using an AR3 but I have an AR2, so I guess icons on the headunit are different.
On my phone side I get a Bluetooth symbol with 6 dots as well, and it's working.
Area51© said:
Hmmm, basically that part (Bluetooth communication etc.) is not changed from the original app. So I don't really understand why there is a difference. It seems you are using an AR3 but I have an AR2, so I guess icons on the headunit are different.
On my phone side I get a Bluetooth symbol with 6 dots as well, and it's working.
Click to expand...
Click to collapse
hmmmm. I uninstalled the app, restarted the phone, reinstalled, gave root access, and still nothing =(. I made an album of screenshots and pics http://imgur.com/R7sU3gf,vBVOGAN,VAiII0J,U5NEyBC#3 . When I go to the center icon it gives me a message like app radio does not seem to be installed, when I hit ignore, I see the home screen of android, but I get that hand with the x when I try to do anything.
enjoimadcow said:
hmmmm. I uninstalled the app, restarted the phone, reinstalled, gave root access, and still nothing =(. I made an album of screenshots and pics http://imgur.com/R7sU3gf,vBVOGAN,VAiII0J,U5NEyBC#3 . When I go to the center icon it gives me a message like app radio does not seem to be installed, when I hit ignore, I see the home screen of android, but I get that hand with the x when I try to do anything.
Click to expand...
Click to collapse
Phone side is same as I get. AppRadio side I can't compare I have an AR2.
On the phone side I only get that Bluetooth icon with the 6 dots. I think the other is because you have Bluetooth streaming.
lpasq said:
Try this https://docs.google.com/forms/d/1sz8ItL_d4NlLWP33-JK1aaxv8-LWZGuKPjr1RuMNlBI/edit?usp=sharing
Area51...paste link to OP if it works for you.
Click to expand...
Click to collapse
Thanks.
This link got me into the design mode somehow. Do you have to give everybody access before they can enter data?
Maybe a field to state working or not working and if not, why not would be nice.
Will look at it later, my gf wants me to watch the last episode of Dexter now.
lpasq said:
Try this https://docs.google.com/forms/d/1sz8ItL_d4NlLWP33-JK1aaxv8-LWZGuKPjr1RuMNlBI/edit?usp=sharing
Area51...paste link to OP if it works for you.
Click to expand...
Click to collapse
I tried it again but now I got a message that the file is in the owners bin. When I clicked the link, I entered into design mode or something. I had to click "View live form" to enter data. But it seems someone else entered data in design mode and replaced all the titles with the answers he wanted to give. Do you have a copy? Maybe need another link to go to the View live form mode right away.
enjoimadcow said:
hmmmm. I uninstalled the app, restarted the phone, reinstalled, gave root access, and still nothing =(. I made an album of screenshots and pics http://imgur.com/R7sU3gf,vBVOGAN,VAiII0J,U5NEyBC#3 . When I go to the center icon it gives me a message like app radio does not seem to be installed, when I hit ignore, I see the home screen of android, but I get that hand with the x when I try to do anything.
Click to expand...
Click to collapse
Have you paired the radio to the phone under Bluetooth settings? Also - check if phone is "selected' on the connection tab on the radio itself (I recommend auto connection to be set to ON)
Hi, i only know of Cyanogenmod having built-in Volumemediakey-Functions but is there perhaps another, faster and still stable rom, that has these? The thing is that all the xposed modules (that i know) that do the same thing do that even when no music is playing and i don't want that
And Cyanogenmod while being very good i feel like there is room for improvement and also it couldn't be set to always connect as USB Device with my computer (it always connected with "charging only" despite my different settings in developer options)
Much thanks in advance
Edit: And also, is it adviseable to flash a kernel as well? Or are they integretated even? I've never done that before don't know if i should... Plus i don't know if need to be warry of kernel change or not. Maybe one kernel comes with an included kernel and then i change but the next one doesn't have an included one. So then i would have to flash another kernel or doesn't it matter??
Edit: So far i have found out Exodus has this feature as well.
Don't know if it's any better than CM13 otherwise but will keep on searching ..
Edit: Okay nevermind... i went with CM13 again, it seems like the USB thing has been fixed so i am happy with it.