Hi there,
I am using [ROM] NardROM 0.1 with ICS. This firmware is no longer supported.
I am happy with the ROM with the exception of the GPS taking very long to work.
Is there any way someone can upload the GPS files so that I can just replace those?
I have tried with Google Navigation, Sygic and Route 66. The phone is also placed at a point with direct access to the clouds.
Thank you.
This fixed my GPS issue...
carpediem said:
Hi there,
I am using [ROM] NardROM 0.1 with ICS. This firmware is no longer supported.
I am happy with the ROM with the exception of the GPS taking very long to work.
Is there any way someone can upload the GPS files so that I can just replace those?
I have tried with Google Navigation, Sygic and Route 66. The phone is also placed at a point with direct access to the clouds.
Thank you.
Click to expand...
Click to collapse
I'm using IcePop 1.3 right now and it would NEVER get a GPS lock until I applied what I found in this thread - http://forum.xda-developers.com/showthread.php?p=24763092. I'm on AT&T so I applied that specific build and my first GPS lock happened in under a minute! Subsequent locks happen in about 5 seconds. THIS is how a GPS should work!
Anyway YMMV, depending on your carrier, etc, but that thread seems to have a custom build for everyone's setup. Check it out.
sleeeves said:
I'm using IcePop 1.3 right now and it would NEVER get a GPS lock until I applied what I found in this thread - http://forum.xda-developers.com/showthread.php?p=24763092. I'm on AT&T so I applied that specific build and my first GPS lock happened in under a minute! Subsequent locks happen in about 5 seconds. THIS is how a GPS should work!
Anyway YMMV, depending on your carrier, etc, but that thread seems to have a custom build for everyone's setup. Check it out.
Click to expand...
Click to collapse
my rom has a working gps ...
thread needs moved...
Moved...and please next time hit the report button. Thank You.
I've been suffering with this on and off continually... I managed to fix it then, it would go wrong less than a week later.
Began butchering the gps/sirfgps.conf files without really knowing precisely what to chop change - but then stumbled across a great config:
SIRFGPS.conf (truncated)
###
EXTERNAL_LNA=1
UART_BAUD_RATE=2
FREQUENCY_AIDING=1
SENSOR_AIDING=0
SSL_ENABLED=0
CP_RESPONSETIME=3
ATT_NETWORK_OPERATOR=0
ICS_NETWORK_OPERATOR=0
###
GPS.conf (complete)
###
NTP_SERVER=europe.pool.ntp.org
###
XTRA_SERVER_1=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra1.gpsonextra.net/xtra.bin
###
INTERMEDIATE_POS=1
ACCURACY_THRES=1000
###
Takes between 9-16 secs on average to lock, which has changed my life - I use GPS every day to track my cycling and used to have to wait a solid 3mins or remember to switch it on 5min in advance.
Running UCLAJ3 stock rooted.
Where are you located? These GPS looks to be for Europe..
yohan4ws said:
Where are you located? These GPS looks to be for Europe..
Click to expand...
Click to collapse
The NTP server is just for time, and all the world's NTP servers output in GMT anyway, so that won't be a problem.
melvatron said:
I've been suffering with this on and off continually... I managed to fix it then, it would go wrong less than a week later.
Began butchering the gps/sirfgps.conf files without really knowing precisely what to chop change - but then stumbled across a great config:
SIRFGPS.conf (truncated)
###
EXTERNAL_LNA=1
UART_BAUD_RATE=2
FREQUENCY_AIDING=1
SENSOR_AIDING=0
SSL_ENABLED=0
CP_RESPONSETIME=3
ATT_NETWORK_OPERATOR=0
ICS_NETWORK_OPERATOR=0
###
GPS.conf (complete)
###
NTP_SERVER=europe.pool.ntp.org
###
XTRA_SERVER_1=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra1.gpsonextra.net/xtra.bin
###
INTERMEDIATE_POS=1
ACCURACY_THRES=1000
###
Takes between 9-16 secs on average to lock, which has changed my life - I use GPS every day to track my cycling and used to have to wait a solid 3mins or remember to switch it on 5min in advance.
Running UCLAJ3 stock rooted.
Click to expand...
Click to collapse
In GPS.conf, did removing the below lines help, or they were never there to begin with ?
SUPL_HOST=supl.google.com
SUPL_PORT=7276
Have ever tried adding this line which I've seen in other threads ?
AGPS=http://xtra3.gpsonextra.net/xtra.bin
Are you using another App such as "GPS Status & Toolbox" to pull down the AGPS data ?
Maruzko said:
In GPS.conf, did removing the below lines help, or they were never there to begin with ?
SUPL_HOST=supl.google.com
SUPL_PORT=7276
Have ever tried adding this line which I've seen in other threads ?
AGPS=http://xtra3.gpsonextra.net/xtra.bin
Are you using another App such as "GPS Status & Toolbox" to pull down the AGPS data ?
Click to expand...
Click to collapse
Removing it helped better than having it in...
It seems most of the extra gps settings you can put in our gps.conf are more hinderance than help on our devices, I had everything possible in there at one point.
Then began trying different combinations of settings by just adding to the default 4 lines... that SUPL line wasnt one of them.
The intermediate position definitely seems make a difference though, but it has been highlighted before on other threads that the sirfgps.conf is critical to get right also.
________________________________________________
Samsung SGH-I927 | Android 4.0.4 | XDA App
I just want to confirm that after editing my GPS.conf and sirgps.conf to the above (and no other changes after flashing to stock rooted by Dman) my GPS fixed in mere seconds using WAZE ... I also have GPS Status installed.
I'm reverting back to stock ICS rooted because of the wake lock issues... Lack of GPS lock was the only reason I went to JB, this appears to have fixed it.
melvatron said:
I've been suffering with this on and off continually... I managed to fix it then, it would go wrong less than a week later.
Began butchering the gps/sirfgps.conf files without really knowing precisely what to chop change - but then stumbled across a great config:
SIRFGPS.conf (truncated)
###
EXTERNAL_LNA=1
UART_BAUD_RATE=2
FREQUENCY_AIDING=1
SENSOR_AIDING=0
SSL_ENABLED=0
CP_RESPONSETIME=3
ATT_NETWORK_OPERATOR=0
ICS_NETWORK_OPERATOR=0
###
GPS.conf (complete)
###
NTP_SERVER=europe.pool.ntp.org
###
XTRA_SERVER_1=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra1.gpsonextra.net/xtra.bin
###
INTERMEDIATE_POS=1
ACCURACY_THRES=1000
###
Takes between 9-16 secs on average to lock, which has changed my life - I use GPS every day to track my cycling and used to have to wait a solid 3mins or remember to switch it on 5min in advance.
Running UCLAJ3 stock rooted.
Click to expand...
Click to collapse
Thank you for sharing this. Can you give steps please on how you did that? because I dont know what to do to fix and where to start.
I tried to use the three methods in One X forum but none of them worked. Or, better say, I couldn't get to the end of the process: the file is read-only (adb method), the file cannot be overwritten (total commander method) and process failed (cwm method).
Uff.
Ok, Here's what I did (In a nutshell..)
On my ROOTED ICS installation (Dman's Rooted ICS w/ AOKP lockscreen ... ps, I don't recommend this one, get his rooted deodexed WITHOUT aokp lock screen, it's been giving me issues) ... I installed ES Explorer and set it up in the options to allow read/write to System.
I browse to /system/etc opened up gps.conf and sirgps.conf with ES Note Editor
I then removed all the lines for gps.conf ...and ensured it looked exactly as above.
sirgps.conf I made the changes on every line as shown above and left everything else there.
This should be the simplest method... if an absolute step by step with pictures is required I will create a new post for everyone to use.
R: GPS takes forever... Can i replace the GPS files?
I'll try this later this afternoon then.
[sent from my awesome Samsung Captivate Glide]
[AT&T rooted stock ROM]
The most important thing to edit is SIRFGPS.conf - once that's changed, the phone locks GPS almost immediately. Make sure you have a file manager that can take root privileges, so that you can alter the .conf files in the first place.
Bear in mind that this is a ICS thing; in various JB ROMs I've tried I never had to do any GPS file tinkering.
Kombatant said:
The most important thing to edit is SIRFGPS.conf - once that's changed, the phone locks GPS almost immediately. Make sure you have a file manager that can take root privileges, so that you can alter the .conf files in the first place.
Bear in mind that this is a ICS thing; in various JB ROMs I've tried I never had to do any GPS file tinkering.
Click to expand...
Click to collapse
Thanks. Well, I run a gingerbread rom, could it work?
Such a shame the adb method didn't work, it looked quite easy.
---------- Post added at 02:06 PM ---------- Previous post was at 01:47 PM ----------
yohan4ws said:
Ok, Here's what I did (In a nutshell..)
On my ROOTED ICS installation (Dman's Rooted ICS w/ AOKP lockscreen ... ps, I don't recommend this one, get his rooted deodexed WITHOUT aokp lock screen, it's been giving me issues) ... I installed ES Explorer and set it up in the options to allow read/write to System.
I browse to /system/etc opened up gps.conf and sirgps.conf with ES Note Editor
I then removed all the lines for gps.conf ...and ensured it looked exactly as above.
sirgps.conf I made the changes on every line as shown above and left everything else there.
This should be the simplest method... if an absolute step by step with pictures is required I will create a new post for everyone to use.
Click to expand...
Click to collapse
does this mean that you erased the whole text of gps.conf and just pasted this:
###
NTP_SERVER=europe.pool.ntp.org
###
XTRA_SERVER_1=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra1.gpsonextra.net/xtra.bin
###
INTERMEDIATE_POS=1
ACCURACY_THRES=1000
###
?
sbiricuda said:
Thanks. Well, I run a gingerbread rom, could it work?
Such a shame the adb method didn't work, it looked quite easy.
---------- Post added at 02:06 PM ---------- Previous post was at 01:47 PM ----------
does this mean that you erased the whole text of gps.conf and just pasted this:
###
NTP_SERVER=europe.pool.ntp.org
###
XTRA_SERVER_1=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra1.gpsonextra.net/xtra.bin
###
INTERMEDIATE_POS=1
ACCURACY_THRES=1000
###
?
Click to expand...
Click to collapse
You know you can simply rename your existing gps.conf to gps.bak or something, try every suggestion and if it's not good revert to the old one, right?
I'm not afraid of losing the original file (I have lots of backups too), i'm just not so sure I understood what i have to do
---------- Post added at 08:21 PM ---------- Previous post was at 07:22 PM ----------
Ok, i did it.
I fixed with FasterGPS from the Market. I already tried with it but it didn't work. That's why i tried to patch as described in the One X forum.. no luck.
I must really suck with modding, given that my editing was so bad gps didn't even turn on. Lol. I tried many different ways, even editing only sirfgps.conf .. no luck.
FasterGPS apparently did the miracle and i had a lock in 10 seconds.
Thank you guys for your help
im curious to what FasterGPS did, maybe you can paste your gps.conf and sirgps.conf content here for us to critique and analyze ?
Related
The last days Froyo rubbed all my nerves. As promised earlier to a few members I decided to update CM5-builds. And here is the first Final release of my Eclair-builds:
VaniljEclair from kalt_kaffe (original thread from HTC Kaiser)
Changelog:
[*]V1.1 is a 1-file-download. The ZIP-Archive contains everything you need!
What's Included:
Latest LauncherPro
Compcache activated
Browser removed and replaced by Dolphin Browser HD
Performance tuning
[*]1-file-download due to FINAL release V1.1 -> read Install Instructions carefully!
To get the full performance out of all my builds you have to open all apps once and then restart your device 1-2x times
Known Bugs:
Camera is broken
If you wake up your device and the screen stays black -> just slide from left to right as you would do when unlocking the phone -> The display will wake up immediately.
Used sources for this Port:
kalt_kaffe's VaniljEclair ROM for HTC Kaiser
XDAndroid: rootfs + kernel (2.6.27)
Credits go to: Cyanogen + Cyanogen-Team, kalt_kaffe, XDAndroid-Project, Balsat and top everyone else whom I have forgot! You may consider a donation to all of 'em!
Download + Installation Instructions (read carefully):
Neopeek's VaniljEclair-Port CyanogenMod 5.0.8
RE-EDIT: This Text is copy&paste for all threads on all compatible devices! Everything works fine for my Diamond. I still have no other device then a Diamond. I am still a one-man-show regarding my Android-Ports. So don't blame me for anything that doesn't work for you on any other device...
thank you very much
Can you post some screens please....
Hi vatoloco,
I couldn't see anything run on my Blackstone,always show black screen.
Thanks for the good work
mike86_tsai said:
Hi vatoloco,
I couldn't see anything run on my Blackstone,always show black screen.
Thanks for the good work
Click to expand...
Click to collapse
me too,it`s always show black screen
try turning off 3d in startup...
vatoloco said:
try turning off 3d in startup...
Click to expand...
Click to collapse
How can i do it? where?
always black screen, what to do?
Finally, I can see the main screen, just follow the below setting
Originally Posted by NemanjaLO View Post
Got it WORKING without force close!!!
Before first boot edit your startup.txt and add this to "set cmdline" "hw3d.force=1" and keep TouchFlo running in WinMo. You also need to disable boot animation in tar.gz package: For this you need linux system, open your archive in linux and find init.eclair.rc file in init.cfg folder and disable this lines:
#service bootanim /system/bin/bootanimation
# user graphics
# group graphics
# disabled
# oneshot
But after boot , I could turn on the wifi,but couldn't get ip.
GPRS ok.
Bluetooth ok,but the voice have a lot of noise,microphone ok.
GPS ok.
speed is good.
Thanks for the good work
you dont have to do that anymore, hw3d is working, but gralloc from the "hw3d thread" has to be replaced to /lib/eclair/hw/ & /system/lib/hw/ and also for me wifi wont work if i use updated kernel. so i extract wlan.ko from the modules and place it to /system/lib/modules/ ...
overall the build seems stable.
# I get 16.5 fps on neocore benchmark. (pretty decent i believe)
#However i am facing issues with wifi not able to get dhcp address (have to set static)
# google talk and gmail app aint working (force close). need to probably replace the apps. (not sure)
thanks neopeek.
vatoloco said:
Camera is broken
Click to expand...
Click to collapse
Means: Not working or really broken???
First post updated with V1.1
Broken means not working!
For those who got this release working .
can you upload the files that you had to modify (startup,tar.gz...) , so it would be a more easier process for non-experienced users to download this release and run it by one button ..
thanks in advance .
Where's the problem, huh? Move to npkinstall-folder. rename diamond.txt to startup.txt there! Start install.exe! After installation move to startups-folder and copy startup.txt from diamond where haret.exe is and simply run haret.exe! That's all! Sometimes I ask myself if someone misses reading my instructions. I think renaming 1 txt-file and copying 1 txt-file should be simple enough!
That's 2 steps!
Neopeek,
For blacstone users, need to replace the gralloc file in your builds to get the hw3d working. which if not done gives black screen and 3d is not enabled.
Neopeek,
For blacstone users, need to replace the gralloc file in your builds to get the hw3d working. which if not done gives black screen and 3d is not enabled.
Click to expand...
Click to collapse
...but boots up for you w/o that gralloc? So kindly link me to that gralloc so I can implement it. But first if it boots up just let me know if everything else works or something Blackstone-specific still needs a fix. Damn it! I have no Blackstone. SO I need you to test and give me hints!
I'm going to format to ext2 partition to try
Many thanks for the chance to get android on my blackstone man
I already downloaded the v1.1,but when I run the installer, the system show it will formate my ext2 partition,and then say cann't open xxxx.tar.gz,when show reboot in 7 seconds.But nothing happen after 7 seconds.
When I reboot manually,I found all of the android I in my card was gone,it empty because the sdcard already be formate during the installer running.I try two times the result is the same.
Fix already,It's my problem, I don't know why between the ext2 and fat32, there is 7.8MB no use, so after I repartition my sdcard, now is ok to install the file.
After waiting over 20 minutes, still black screen.
Neopeek,
For blacstone users, need to replace the gralloc file in your builds to get the hw3d working. which if not done gives black screen and 3d is not enabled.
Click to expand...
Click to collapse
I think I have to include this for you to get it working for you. On the other side you may try to set "hw3d.force=0" in startup.txt. Thanx indeed for testing!
Yes, after replace the gralloc.msm7k.so that from hw3d thread, now it boot ok. after boot the wifi is also no problem to get ip.
Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for RAPH/DIAM) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location)
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
DIAM users have reported the g-sensor is flipped -
emc02 said:
ok, the solution for DIAM100 is:
change "gsensor_axis=2,-1,3" to "gsensor_axis=-2,1,3"
works perfect!
Click to expand...
Click to collapse
This line should be in the startup.txt file if that wasn't obvious .
Thanks to emc02 for that solution!
The keyboard should be fine, but I've had some Blackstone users complain - if you want, switch the keyboard out with another. mr_grisha's original post.
Anything that's broken in Froyo, is probably broken in this build.
Changelog March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Strange, I never saw the calib. screen. Probably because I just replaced the system.ext2 file and let it run it's course? I do recall there being calib. "issues" with 1253 because the text would continue to scroll even while you were attempting to tap the points.
[R^7Z EDIT]I don't suppose that would work if you were re-working this from the beginning or starting over from scratch (doh!). Lucky me, I save just about every new/update regardless of kernel package or rootfs update[/R^7Z EDIT]
R^7Z said:
Strange, I never saw the calib. screen. Probably because I just replaced the system.ext2 file and let it run it's course? I do recall there being calib. "issues" with 1253 because the text would continue to scroll even while you were attempting to tap the points.
Click to expand...
Click to collapse
If you already have a ts-calibration file, there's no need to create a new one .
A note to all troubled users
And additionally, to those who are reporting issues, it would behoove you to help the devs out by not making them guess what you are using (device) to include but not limited to, which rootfs and kernel package (date of release and commit ID might be helpful). That being said, be aware of what you are talking about (app discussion should not fall into this thread) and please keep talks of neopeek variants to a minimum (I know a little bit about these builds and will help out where I can, PM me if you really think I can help and if you really need some assistance)
arrrghhh said:
[CUT]
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
I noticed the (virtual) keyboard is comically tiny. Seems to work fine tho...
[CUT]
Click to expand...
Click to collapse
Noticed the same thing in neocore (30fps without textures) but quadrant 3D tests looked good. Probably we need to test more apps.
Virtual keyboard is unusable on Blackstone. All buttons are tiny and kind of stacked together at the bottom of the screen.
BTW. I can't calibrate the screen since .35 FB commit (17 Dec). I think it's because of FB debug spam - this should be easy to fix.
on ralph100 i've been stuck on "busy" loop for about 20mins now.
loops saying "INFO task rpcrouter: 15 blocked out for more than 120 seconds"
thebranded said:
on ralph100 i've been stuck on "busy" loop for about 20mins now.
loops saying "INFO task rpcrouter: 15 blocked out for more than 120 seconds"
Click to expand...
Click to collapse
Hrm. I'm going to go with format your SD card using the HP Tool. Full format, FAT32.
Also, might want to try kernel 1258. Let me know if neither of those things improve it. Is it creating a data.img...?
g3rm0 said:
Noticed the same thing in neocore (30fps without textures) but quadrant 3D tests looked good. Probably we need to test more apps.
Virtual keyboard is unusable on Blackstone. All buttons are tiny and kind of stacked together at the bottom of the screen.
BTW. I can't calibrate the screen since .35 FB commit (17 Dec). I think it's because of FB debug spam - this should be easy to fix.
Click to expand...
Click to collapse
Sorry forgot to respond to this. Two things, there's an app called "gingberbread keyboard". Find it on the market, see if it works better for you.
Second, I've heard the new 1258 kernel is fixed - not sure how, but it seems the clocks commit from jb's tree did it.
works with 1258, did reformat SD card.
Still had issue with not seeing the touchscreen calibration though, just copied over a old TS file.
thebranded said:
works with 1258, did reformat SD card.
Still had issue with not seeing the touchscreen calibration though, just copied over a old TS file.
Click to expand...
Click to collapse
Glad it's working for you. I think we've narrowed down the calib issue, so hopefully we'll get that fixed for all devices soon. Not sure why but RHOD's don't seem to have the issue any longer - no matter, we will get it resolved for all devices. Sometimes just takes longer for the old devices unfortunately...
[xda Link] Gingerbread keyboard
For those of you who need it, check THIS thread out!
n-Joie! (Enjoy)
R^7Z said:
For those of you who need it, check THIS thread out!
n-Joie! (Enjoy)
Click to expand...
Click to collapse
I've heard it doesn't work... Per another user, I have added a different recommendation:
arrrghhh said:
I noticed the (virtual) keyboard is comically tiny. Seems to work fine tho... If it does bother you, user "webxplore" said the app "gingerbread keyboard" (on the Market) fixes the issue. Thanks webxplore!
Click to expand...
Click to collapse
Gingerbread keyboard (market version)
Will see about getting the market version upped for those who are not able to access a wifi or have the awesome pull-out keyboard the RAPH/TP has
[R^7Z EDIT]Keep in mind, I have a RAPH110/TP/at&t Fuze
Free for all!
n-Joie! (Enjoy)
[/R^7Z EDIT]
Please note, we now have a source fix for the keyboard size and it will be integrated in the next testing image.
Not sure why WiFi works better in GB than FroYo but I just disabled and re-enabled like several times, without fail/error. I'm using the packaged build found in this thread and using Glemsom's kernel package for the 14th. If needed, I can supply screenshots.
R^7Z said:
Not sure why WiFi works better in GB than FroYo but I just disabled and re-enabled like several times, without fail/error. I'm using the packaged build found in this thread and using Glemsom's kernel package for the 14th. If needed, I can supply screenshots.
Click to expand...
Click to collapse
No need. I'll let stinebd know, I'm not sure what the difference would be... if he can backport something to Froyo, or if we are just going to be moving forward and focusing on GB. Thanks again for testing!
Thanks alot man this build is great! seems to boot and run faster and smoother then froyo ever did for me...only issues i ran into were not being able to see the calibration which if youtap on the screen it glitches and shows part of it.....but the main thing is i seem to have a problem staying connected to the internet and have to soft reset to get it working again....also airplane mode seems to get stuck once clicked and only a soft reset fixes it
m using this one is there anyway to chnge keyboard cx buttons are to small and my phone doesnot rotate any help
xtremists said:
m using this one is there anyway to chnge keyboard cx buttons are to small and my phone doesnot rotate any help
Click to expand...
Click to collapse
Read the second post. Gsensor doesn't work yet, but there's a fix in the pipeline. Keyboard fix as well, in the meantime... read the second post!!!!
Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for RHOD/TOPA) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog
Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location). I think this also breaks the stock browser, I recommend using Dolphin Mini!
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
Data - very flaky - CDMA users have data break for them after every phone call, and GSM users seem to have better luck but it's not flawless. Even seen reports of wifi having issues with data not going out to the WAN. There is a bug filed on this issue.
Anything that's broken in Froyo, is probably broken in this build. Although what is interesting, I noticed that in this build I don't have the landscape-on-boot issue that I get with Froyo...
Changelog March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)
Works good so far
Been using this for about 3 hours so far. Here's a little review. Upgraded through Stinebd's link in the XDAndroid thread (same as this I guess, but the arggggh's complete package includes all files needed). I deleted the data.img and replaced my system2 file. The first boot set itself up and then rebooted to winmo. The second boot worked. I was able to download Titanium backup from the market and restore my apps that I was using in Froyo. Overall it was working well. The default keyboard is tiny on my screen. My data connection is a little finicky as it was working when I restored my apps, but I could not connect after a while (same thing happened in my Froyo build periodically). As far as speed is good and bad, sometimes it's quick, other times it's quite slow. Overall, it's pretty good considering it was just released to us. Looking forward to future builds.
Edit: I reused my calibration file from Froyo. No issues
Rhod400, 2/10 Zimage and Rootfs from GIT
mmm, I may be blind but I can't see any download link! I'd like to test it and let you know!
anyway I already want to thank you for the hard work!
The system file was posted by stinebd in this thread:
http://forum.xda-developers.com/showthread.php?t=627997&page=1226
Thanks, I've included the original link to stinebd's post in my first post.
Still working out kinks, and stine will probably want me to host it on files.xdandroid.com - sorry for the delay... It will be here soon .
so this is the neopeek build only in an image?
husam666 said:
so this is the neopeek build only in an image?
Click to expand...
Click to collapse
This has nothing to do whatsoever with neopeek. This is AOSP code, modified to work on our phones. The system image work is done entirely by stinebd, and I have made a bundle - Link up!
arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
edit- nvm I reread it a 5th time and understood heh
randomblame said:
arrrghhh any idea what the kernel incompatibility comes from? Thats strange...
Click to expand...
Click to collapse
You mean the calibration issue? Some commit broke it, not sure which one. There's rumors that we can read it from the spl, then we won't need a kernel-based calibration - we'll be able to do it in userland, which is really what we want especially going forward to NAND.
Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?
JBS2 said:
Gonna try this release this weekend
rhod100 does have the same panel problems as on a FRX04 release a guess?
Click to expand...
Click to collapse
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.
arrrghhh said:
Panel problems are kernel related, not system image related.
What kernel do you run FRX04 on...? Thanks.
Click to expand...
Click to collapse
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.
JBS2 said:
Most recent from your testing topic.
Panel wakes up very slow normally or after touching the screen or power button multiple times.
Click to expand...
Click to collapse
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...
arrrghhh said:
Ah. Again, that's a testing kernel. Let's keep testing kernel discussion in that thread and build talk about this build in this thread... Thanks...
Click to expand...
Click to collapse
I know, you asked which kernel I was using
Just wondering if these release has something to do with the panel issues but I realize this is a kernel related problem.
Keep up the goog work, I'll keep testing the testing kernels to see if the known problem could be fixed
Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).
steyn_e said:
Okay, here's my 2cents:
BTW, i use rhod100.
Hardware3d doesn't work because the line is missing from the startup (as far as i am concerned, maybe you removed it on purpose).
Click to expand...
Click to collapse
That entry is no longer required. Put it in and see... Thanks!
this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.
kdub94 said:
this is such an exciting build. It runs really fast. keep up the good work guys. Btw, to get a bigger gingerbread keyboard, search for "gingerbread Keyboard" in the market. its a larger sized version of the one that comes with the rom.
Click to expand...
Click to collapse
I've already included a fix in the second post, thanks!
Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download
Caveat List
CDMA users might get a crash in phone.apk and no service on boot. If waiting doesn't resolve the issue, then reboot. Should come up fine...
BT might still be flaky
The CSV files from my RHOD400 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
GBX0C Changelog
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
Just to get people going on some of the newer kernels.
2.6.35 is currently auto-built at:
https://code.google.com/p/zimages/downloads/list
Emwe has been maintaining this tree, and he is most qualified to speak about it, but pretty much everything is functional barring camera.
Head over to this testing thread for more information on 2.6.39/3.0/3.1 kernels for Rhodium.
arrrghhh said:
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Download
Click to expand...
Click to collapse
You probably saw this problem coming but I have just the stock windows rom, how would i go about doing this? (or do i have to go and find each and every CSV file )
I googled and downloaded total commander on my laptop, and i got it to show my phone, but it only shows up with my SD card stuff, not my phone itself (unless thats whats supposed to happen )
Will keep trying! -determined-
A cool username said:
You probably saw this problem coming but I have just the stock windows rom, how would i go about doing this? (or do i have to go and find each and every CSV file )
I googled and downloaded total commander on my laptop, and i got it to show my phone, but it only shows up with my SD card stuff, not my phone itself (unless thats whats supposed to happen )
Will keep trying! -determined-
Click to expand...
Click to collapse
Sigh, are you freakin serious? I even link to Total Commander's website in my instructions.... Not sure how much easier I could've made it.
I also just attached the CSV's for the lazy... .
It does say TESTING in the title, no? Yea. It does..
Hehehe I know, I know, i guess i just don't have very much knowledge with this kinda stuff (obviously) Thanks!
A cool username said:
Hehehe I know, I know, i guess i just don't have very much knowledge with this kinda stuff (obviously) Thanks!
Click to expand...
Click to collapse
Testing/development threads usually mean "please pitch in and help test if you can. If not, please wait until the final stable release".
Make sense?
Okay, i'll be glad to help test it if someone could post the CSV files for a rhod300 (if its not too much trouble). If not, I will wait for the stable release. Thanks arrrghhh!
Yes, makes sense
Installed the rom but i've got a problem with the fact that the screen dissapaers after about 5 seconds, so i can't even put in my pin.
also i'll put in the csv files from my rhodium100.
Edit: Works good on second boot, had to change the calibration file and it's works good and fast. Only thing i have is that i now have got 919 contacts instead of the (normal) 135.
A lot of text messages for tonight
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Camera works when you don't move a lot, otherwise it's blocked.
bleutooth doesn't work for me it connects to my parrot but i can't make a phone call.
Schumi_wk said:
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Camera works when you don't move a lot, otherwise it's blocked.
bleutooth doesn't work for me it connects to my parrot but i can't make a phone call.
Click to expand...
Click to collapse
Sounds like a proximity sensor issue - not sure if some of the GSM rhod proximity related adjustments made it into the acoustic .27 kernel. You should try one of the newer kernels (not sure what's the status with .35 and GSM-proximity, but on 39+ I expect you won't have this issue).
This GB build, and these new kernels are kexec enabled. Meaning if you are on .35 or newer, and would like to interchange the kernel on-the-go, without re-booting to WinMo you can do the following:
1. While in Android, copy the new kernel and modules to the same location (over-writing the zImage) as your current kernel (adb push).
2. Go to the shutdown menu in GB, and select "Kexec".
3. Phone will reboot within Android, using the new kernel.
Again, this feature only works with the new kernels.
---------- Post added at 06:20 PM ---------- Previous post was at 05:38 PM ----------
Schumi_wk said:
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Click to expand...
Click to collapse
Let me know if you are willing to test a prox support for rhod 100. I'll pm you a kernel pack.
Just tried the .39 kernel and bluetooth didn't work with that one. The phone did work with this one.
Than did the 3.0 kernel and bluetooth works but there i don't have wifi.
The 3.1 kernel doesn't load it stops at
3.711395 mmcblk0:mmc1:1234 SA0BG 7.42gb
3.728118 mmcblk0: p1
Than did the .35 kernel and bluetooth worked but no wifi.
No more testing for me today, i'm getting ready for the last hours of 2011.
For all of you enjoy the last moments of 2011 and start 2012 with a lot of fun!!
Schumi_wk said:
Just tried the .39 kernel and bluetooth didn't work with that one. Than did the 3.0 kernel and bluetooth works but there i don't have wifi. The 3.1 kernel doesn't load it stops at 3.711395 mmcblk0:mmc1:1234 SA0BG 7.42gb
3.728118 mmcblk0: p1
Than did the .35 kernel and bluetooth worked but no wifi.
No more testing for me today, i'm getting ready for the last hours of 2011.
For all of you enjoy the last moments of 2011 and start 2012 with a lot of fun!!
Click to expand...
Click to collapse
You must understand that BT is only functional in 3.0 and .35 (well, and .27). I don't know about the state of wifi in any of 'em... Should work in .39, I thought it worked in .35 as well. Haven't booted .35 in quite some time myself. Logs are really going to be necessary to triage any of your problems tho. Thanks, enjoy New Years.
arrrghhh said:
Caveat List
The CSV files from my RHOD400 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
Click to expand...
Click to collapse
Here are my .csv files for the Tilt2 (Rhod300). Have not compared to the RHOD400 yet.
Here's my CSV files from my RHOD500
BTW, I can't use the Wi-Fi
I'm using the default kernel and settings that came in the bundle...I will try using a new data.img
Logcat says: "E/WifiService< 1328>: Failed to load Wi-Fi driver."
nickleby said:
Here's my CSV files from my RHOD500
BTW, I can't use the Wi-Fi
I'm using the default kernel and settings that came in the bundle...I will try using a new data.img
Logcat says: "E/WifiService< 1328>: Failed to load Wi-Fi driver."
Click to expand...
Click to collapse
You didn't start on a new data.img...?
This makes me think the modules didn't copy, but I force them to every time. Perhaps I should rm them all first... bleh.
You're not mixing and matching anything are you...?
arrrghhh said:
You didn't start on a new data.img...?
This makes me think the modules didn't copy, but I force them to every time. Perhaps I should rm them all first... bleh.
You're not mixing and matching anything are you...?
Click to expand...
Click to collapse
I'm using a new data.img, but the wifi still not work...I'm using the rootfs, zimage, kernel, initrd, startup.txt and system.ext2 that came in the bundle, I just added my ts-calibration
nickleby said:
I'm using a new data.img, but the wifi still not work...I'm using the rootfs, zimage, kernel, initrd, startup.txt and system.ext2 that came in the bundle, I just added my ts-calibration
Click to expand...
Click to collapse
Hrm. Can you pull some logs? I tested wifi every which way and it was always working. I did make some rootfs tweaks, so I guess it's possible it's using the wrong firmware...?
Someone had a wifi issue, rebooted and it went away. I hate wifi .
Yay! Merry Christmas and Happy New Year guys. Can't wait to try this and get back on .39. And sort-of hot-swapping kernels? Sweet.
arrrghhh said:
Hrm. Can you pull some logs? I tested wifi every which way and it was always working. I did make some rootfs tweaks, so I guess it's possible it's using the wrong firmware...?
Someone had a wifi issue, rebooted and it went away. I hate wifi .
Click to expand...
Click to collapse
I rebooted the phone, but it doesn't work...Here's a logcat, if you need another type of logs, please tell me...
nickleby said:
I rebooted the phone, but it doesn't work...Here's a logcat, if you need another type of logs, please tell me...
Click to expand...
Click to collapse
I just see a lot of this
E/WifiService( 1320): Failed to load Wi-Fi driver.
So uh... I think that indicates a modules mismatch? rm -rf /lib/modules and rebootski. I guess I need to make that change in init... copying and extracting every time doesn't work.
Hello everyone.
I've been working on the last few days on porting CM10 (or any AOSP rom really) to our device. I think I got the basics working for now so I'd like to share that with all of you.
1. download the attached file.
2. reboot into twrp
3. factory reset
4. wipe "system"
4. flash the file
5. flash gapps (find it in google).
6. reboot
What's been tested:
-Radio: phone calls work and 4G LTE speeds are intact.
-Audio: Bluetooth audio, A2DP, speaker, headphones and in call audio all work.
-GPS: no problemo.
-Camera: works without a problem if you use a third party app like Pudding Camera, Zoom FX.
What else?
Known issues:
- The stylus doesn't work. Need to investigate.
- Radio crashes every now and then.
- Audio in phone calls requires an initiation phase: make 2 phone calls to any number when you boot up to get audio functional on the 3rd call.
This ROM is tested and should work fine on the following devices:
1. AT&T Note 2
2. T-mobile Note 2
3. International LTE Note 2
Dev talk: The device tree was forked from N7100. Most of the board share the same peripherals so it was a matter of getting the correct defconfig and the correct initramfs. I'm uploading the stuff to my github now so you guys can have a look and perhaps fix the remaining bugs Hopefully this will facilitate getting official support by CM10.
Download link:
initial release: http://www.mediafire.com/?n4occ5rwv2nra7p
Dec 08 update: http://www.mediafire.com/?h1h4658y5555k58 (note. this update is compressed using 7z. Use 7-zip to decompress the archive first and then flash the resulting zip file in TWRP)
Dec 13 update: http://www.mediafire.com/?a6hl8qlv5v261q1
Dec 26 update: http://www.mediafire.com/?lubkf4c7c4h4lzc
Jan 13 update: http://www.mediafire.com/?vafgo52b353pep9 Laggy UI? flash this kernel after flashing this rom
Sources:
you'll need to get my sources to build this copy yourself:
1. vendor blobs. Yes I was nice and added the necessary binaries here. You don't need to adb pull em. Please also note that I did some changes to the smdk4412-common directory as well.
2. smdk4412-common device tree changes.
3. The device tree.
4. RILJ implementation
1. goes to ./vendor/samsung/
2. goes to ./device/samsung/smdk4412-common
3. goes to ./device/samsung/i317
4. apply the patch manually to frameworks/base
To compile, after sourcing the envsetup.sh file: "breakfast i317 & make"
Awesome! Currently downloading it, and will report back with my results.
SMS: Works
Calling: Connects, but no audio
Wifi: Works
4G: Works
GPS: Having a few problems...
Problems:
-AOSP keyboard crashes on boot and won't show up at all. Seems to be the only problem so far.
-Phone randomly froze once while opening the notification panel for around 50 seconds. (trebuchet FC afterwards)
-Unable to access Play store (Server Error messages) -- Flashing an older version of GApps fixed this (October version)
Going to try an earlier version of Gapps. I used the newest one.
To the guys trying to compile the sources with their own custom vendor/device tree, did you run into an issue with the kernel compiling with an error due to not finding firmware/SlimISP_ZK.bin ? The kernel compiles just fine when you cd to that directory and run make but it refuses to do it correctly with a full CM make.
If you guys figured it out , lemme know ! it's the last step I need before publishing my code. That part of the kernel needs to compile correctly otherwise the camera just FCs. I tried changing the toolchain from 4.6 to 4.4.3 but that threw some other errors.
jetrii said:
Awesome! Currently downloading it, and will report back with my results.
SMS: Works
Calling: Works
Wifi: Works
4G: Works
Problems:
-AOSP keyboard crashes on boot and won't show up at all. Seems to be the only problem so far. Could be from the GApps package that I flashed.
-Phone randomly froze while opening the notification panel for around 50 seconds. (trebuchet FC afterwards)
Click to expand...
Click to collapse
awesome. are you with t-mo btw? are you using the same exact device (i317) ?
madmack said:
To the guys trying to compile the sources with their own custom vendor/device tree, did you run into an issue with the kernel compiling with an error due to not finding firmware/SlimISP_ZK.bin ? The kernel compiles just fine when you cd to that directory and run make but it refuses to do it correctly with a full CM make.
If you guys figured it out , lemme know ! it's the last step I need before publishing my code. That part of the kernel needs to compile correctly otherwise the camera just FCs. I tried changing the toolchain from 4.6 to 4.4.3 but that threw some other errors.
awesome. are you with t-mo btw? are you using the same exact device (i317) ?
Click to expand...
Click to collapse
I am on AT&T with the same device. I should probably update my carrier
EDIT: Flashed an older version of Gapps (October 2012) and the play store now works!
madmack said:
To the guys trying to compile the sources with their own custom vendor/device tree, did you run into an issue with the kernel compiling with an error due to not finding firmware/SlimISP_ZK.bin ? The kernel compiles just fine when you cd to that directory and run make but it refuses to do it correctly with a full CM make.
If you guys figured it out , lemme know ! it's the last step I need before publishing my code. That part of the kernel needs to compile correctly otherwise the camera just FCs. I tried changing the toolchain from 4.6 to 4.4.3 but that threw some other errors.
awesome. are you with t-mo btw? are you using the same exact device (i317) ?
Click to expand...
Click to collapse
Yes i did bro. You needed to edit the makefil in the kernel's firmware directory. I recommend that you take a look at the stock Makefile for the stock Kernel to see the difference. The SMDK4412 kernel makes certain assumptions about child devices that it shouldn't.
Sent from my SGH-T889 using xda app-developers app
DarthPiggie said:
Yes i did bro. You needed to edit the makefil in the kernel's firmware directory.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Can you please show me your edits?
Flashed on my tmo note2 and our modem . And it worked data, calls didnt check messages I must have had a bad gapps cuz it wasnt playing nice awesome work
Like above the keyboard wasnt working.. edit: dieu about posting about another device in this thread . Just excited
Sent from my SGH-T889 using xda premium
I can also confirm that the AOSP keyboard crashes and the home button doesn't work.
GPS doesn't seem to be working. According to GPS test, it is able to see a few stateliness, and occasionally connects to them, but it's unable to provide a location in Google Maps.
i'm not having any issues with the keyboard.. hmm
people with issues, make sure you the file isn't corrupted or anything
the md5sum is: 6d4426dc85110ff7a2abb6994e1fc53f
madmack said:
Can you please show me your edits?
Click to expand...
Click to collapse
Towards the beggining of firmware/Makefile:
Code:
ifdef CONFIG_MACH_T0
fw-shipped-$(CONFIG_VIDEO_S5C73M3) += SlimISP_ZK.bin \
SlimISP_GK.bin
else
ifdef CONFIG_MACH_BAFFIN
fw-shipped-$(CONFIG_VIDEO_S5C73M3) += SlimISP_ZK.bin \
SlimISP_GK.bin
else
ifdef CONFIG_MACH_GRANDE
fw-shipped-$(CONFIG_VIDEO_S5C73M3) += SlimISP_GJ.bin
else
ifdef CONFIG_MACH_IRON
fw-shipped-$(CONFIG_VIDEO_S5C73M3) += SlimISP_GJ.bin
else
fw-shipped-$(CONFIG_VIDEO_S5C73M3) += SlimISP_ZD.bin \
SlimISP_GD.bin
endif
endif
endif
endif
Just comment that out. It's hacky, but last I checked, our devices did not need those binaries. They weren't in there to begin with.
jetrii said:
GPS doesn't seem to be working. According to GPS test, it is able to see a few stateliness, and occasionally connects to them, but it's unable to provide a location in Google Maps.
Click to expand...
Click to collapse
Cm had a setting for which gps to use ie: internal bluetooth ect.... check that I knew that but over liked many times edit: noob mistake didn't read the whole post b4 comment my bad
Sent from my SGH-T889 using xda premium
madmack said:
i'm not having any issues with the keyboard.. hmm
people with issues, make sure you the file isn't corrupted or anything
the md5sum is: 6d4426dc85110ff7a2abb6994e1fc53f
Click to expand...
Click to collapse
MD5 checks out fine. Does your GPS work? No luck with mine.
DarthPiggie said:
Towards the beggining of firmware/Makefile:
Code:
ifdef CONFIG_MACH_T0
fw-shipped-$(CONFIG_VIDEO_S5C73M3) += SlimISP_ZK.bin \
SlimISP_GK.bin
else
ifdef CONFIG_MACH_BAFFIN
fw-shipped-$(CONFIG_VIDEO_S5C73M3) += SlimISP_ZK.bin \
SlimISP_GK.bin
else
ifdef CONFIG_MACH_GRANDE
fw-shipped-$(CONFIG_VIDEO_S5C73M3) += SlimISP_GJ.bin
else
ifdef CONFIG_MACH_IRON
fw-shipped-$(CONFIG_VIDEO_S5C73M3) += SlimISP_GJ.bin
else
fw-shipped-$(CONFIG_VIDEO_S5C73M3) += SlimISP_ZD.bin \
SlimISP_GD.bin
endif
endif
endif
endif
Just comment that out. It's hacky, but last I checked, our devices did not need those binaries. They weren't in there to begin with.
Click to expand...
Click to collapse
I tried that you see but the Camera FCs. These binaries are necessary. Do you actually have a functional camera?
It's really strange because if you just go to kernel/samsung/smdk4112 and make defconfig & make. You won't run into that issue. Seems like it's a path setup failure somewhere.
Calling connects but i cant hear anything from the other line, they can not hear me ether.
Also radio seems to keep crash lol.
jetrii said:
MD5 checks out fine. Does your GPS work? No luck with mine.
Click to expand...
Click to collapse
it works fine here. it is able to triangulate me in gps status and in maps.
the daemon spells out a crap ton of info to logcat too though while I'm locked.
In addendum, once we get a nice proper defconfig for the kernel we won't have to worry about such edits.
cmenard look at the defconfig:
Code:
#
# EXYNOS4 Machines
#
CONFIG_TARGET_LOCALE_USA=y
CONFIG_MACH_T0_USA_TMO=y
CONFIG_MACH_MIDAS=y
CONFIG_MACH_T0=y
CONFIG_T0_04_BD=y
CONFIG_EXYNOS_SOUND_PLATFORM_DATA=y
CONFIG_SAMSUNG_ANALOG_UART_SWITCH=1
That is what I have in mine. I borrowed that from the stock kernel. I don't get the build issues, however at runtime something is still trying to load that binary. At least that's what I see in the logcat.
---------- Post added at 06:03 PM ---------- Previous post was at 06:02 PM ----------
madmack said:
I tried that you see but the Camera FCs. These binaries are necessary. Do you actually have a functional camera?
It's really strange because if you just go to kernel/samsung/smdk4112 and make defconfig & make. You won't run into that issue. Seems like it's a path setup failure somewhere.
Click to expand...
Click to collapse
Post the exact error here so I can help. I had the same issues too.
jug6ernaut said:
Calling connects but i cant hear anything from the other line, they can not hear me ether.
Click to expand...
Click to collapse
Second this. I called my T-Mobile line, and although it's able to connect, there is no audio.
madmack said:
I tried that you see but the Camera FCs. These binaries are necessary. Do you actually have a functional camera?
It's really strange because if you just go to kernel/samsung/smdk4112 and make defconfig & make. You won't run into that issue. Seems like it's a path setup failure somewhere.
Click to expand...
Click to collapse
If these binaries are necessary, then why aren't they present in the stock ROM? I can't figure that part out, but perhaps you're correct.
EDIT:
You're right! They are on phone. They are just in strange place: /data/cfw
I am not sure why they are not in /system/vendor/firmware like the others but that's what it is. That binary will load the camera.
---------- Post added at 06:11 PM ---------- Previous post was at 06:05 PM ----------
We'll have to edit the proprietary-files.sh script.
Sent from my SGH-T889 using xda app-developers app