yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] LNJ:
Only difference with Captivate modem is that your upload speed is slower. Download speeds are the same as i9000 modems.
[Captivate Android Development] RichMD:
I didn't realize that was the only difference. Why does everyone make a big deal about it then? For the vast majority of us, we upload very little. Download speed is what "most" people care about.
[Captivate Android Development] s1l3nt:
yea but its not really a big deal though
[Captivate Android Development] ninjuh:
I'm just running whatever this ROM comes with which I'm assuming is rfs. Give it a shot anyways, works great.
[Captivate Android Development] shoman94:
I would.... but I don't wanna change my phone from MIUI so.... If I can find another cappy to test with I will. I am looking around.
[Captivate Android Development] DaUnderSheriff:
HSUPA is important

From the standpoint of your overall throughput, you will maintain a faster overall connection when your upload data stream is faster than the HSUPA disabled will support. When you're talking about your overall data experience, the faster your transmitting packets, the faster your able to get server returns and then begin your transition from page to page, or file to file.

Unfortunately, I'm going to go back to Apex, as the experience was great and HSUPA is a deal killer for heavy bandwidth suckers like me...
[Captivate Android Development] shoman94:
Its not the only difference. Ping time is cut in half and download speeds are also increased.
[Captivate Android Development] watsa:
and thats why you have both options available :)
[Captivate Android Development] mrhaley30705:
Ok, so you have an I9000 based ROM and a Captivate based ROM. What's next? MIUI/CM7?
[Captivate Android Development] RichMD:
I may be missing something but latency is going to be the same either way which would affect how soon the server sees your request. If it is only bandwidth being throttled on upload and if you aren't uploading enough to consume the available bandwidth then it makes no difference at all - at least nothing you would ever notice. I'm very familiar with computer networks and I assume this is the same. When you click on something, search, etc, very little data is sent and I doubt it saturates the available upload bandwidth. If you are uploading pictures, video, etc - that's a different story. Your overall connection speed "should" appear the same if you are a "typical" user that wouldn't saturate upload speed. I could be wrong about this but please explain where the logic is wrong.
[Captivate Android Development] watsa:
lol I am the biggest noob when it comes to them :o
[Captivate Android Development] LNJ:
You're right, when doing general web browsing, very little data is uploaded so it makes zero difference.

It only matters when you are uploading big files.

Same with your home ISP. I had dsl with 10mb down and 1mb up in my old place and now I have cable with 10mb down and 500kb up....Internet speed is the same for downloads and browsing but not for uploading. Especially when seeding a torrent!

I still get close to 5mbps on this kh3 modem after 1am just like I did on the good i9000 modems.
[Captivate Android Development] Krynn!:
I've done pretty much the same things and am also seeing WeatherBug continuously force closing...

Logcat gives me this:

I/ActivityThread( 8414): Pub com.aws.searchauthority.elite.locationQuery: com.aws.android.lib.search.LocationSuggestionProvider
I/ActivityThread( 8414): Pub com.aws.android.weatherbug.elite.weatherprovider: com.aws.android.content.WeatherContentProvider
W/dalvikvm( 8414): Unable to resolve superclass of Lcom/aws/android/Typhoon; (364)
W/dalvikvm( 8414): Link of class 'Lcom/aws/android/Typhoon;' failed

I've also found that GasBuddy refuses to acknoledge GPS positions, though it doesn't give an error in logcat.

AT&T Mark the Spot also force closes:

E/dalvikvm( 8926): Could not find class 'com.google.android.maps.GeoPoint', referenced from method com.att.android.markthespot.MarkTheSpot.<init>
W/dalvikvm( 8926): VFY: unable to resolve new-instance 821 (Lcom/google/android/maps/GeoPoint;) in Lcom/att/android/markthespot/MarkTheSpot;

If I had to guess, it looks like there's something screwy in the GPS subsystem that's not letting some apps talk to it properly. But it only appears to be some, as there are other location-aware apps I've tried that work just fine.

I'm not sure if this is related or not, but OS Monitor is also throwing force closes:

W/dalvikvm( 1899): Unable to resolve superclass of Lcom/eolwral/osmonitor/networks/NetworkList; (207)
W/dalvikvm( 1899): Link of class 'Lcom/eolwral/osmonitor/networks/NetworkList;' failed
E/dalvikvm( 1899): Could not find class 'com.eolwral.osmonitor.networks.NetworkList', referenced from method com.eolwral.osmonitor.OSMonitor.onCreate
W/dalvikvm( 1899): VFY: unable to resolve const-class 184 (Lcom/eolwral/osmonitor/networks/NetworkList;) in Lcom/eolwral/osmonitor/OSMonitor;
[Captivate Android Development] FirstNoobToBrickHisPhone:
delete
[Captivate Android Development] LNJ:
I get FCs on Poynt and GasBuddy won't acquire a gps location for some reason even though maps does!
[Captivate Android Development] Krynn!:
Yeah, both Poynt and Glympse force close on me as well.

Ok, how's this for screwy - and maybe indicative of the problem. Open up a GPS Status. I've got lock with just 1 satellite?!? Accuracy to 32 feet? WTF? Ok, Open up GPS Test... Also have lock with just one satellite? Oh wait, there's a second one... with a signal strength of 221?!?!?!?

I'm not sure exactly how all the programs that are force closing are trying to use the GPS, but I'm thinking that they might be freaking out from seeing data that is just way out of bounds, such as insane signal strengths and impossible locks. Or maybe the wonky data is just what I'm able to see of a deeper problem.

Other than that, the rom runs great! ;)
[Captivate Android Development] smully1:
@ Watsa, are there any additional modems available for KH3??
[Captivate Android Development] JordanElliott:
Lmao. Watsa i thanked like 20 of.your posts in this thread. And it finally said thanks button deny or something
[Captivate Android Development] watsa:
1. Have u changed SUPL settings?

2. There are many apps that do work and I am looking into the problem.
[Captivate Android Development] watsa:
lol u seem to be enjoying this now
[Captivate Android Development] JordanElliott:
Hmm did it work? How many thanks do u have now
[Captivate Android Development] xpakage:
Plus 1 who has one satellite which has anywhere between 150 and 230 signal strength.

I had to look up and make sure the government hadn't moved one closer to the house :eek:

Patiently sitting here in my tinfoil hat ;)
[Captivate Android Development] JordanElliott:
Guess ill have to just do it again tomorrow when i get my.5 thanks.:p
[Captivate Android Development] JordanElliott:
Lmaoooo are you really?
[Captivate Android Development] LNJ:
This is the speeds I get before midnight. As you can see the upload speeds are pathetic but it is very consistent compared to the i9000 modem upload speeds!

And I'm on data all day and web surfing is not slow at all!
[Captivate Android Development] shoman94:
wow.... kh3 is an impressive non-hsupa modem. Thanks for the screen shot....
[Captivate Android Development] Krynn!:
No, I haven't... So I just did. I changed the SUPL settings to supl.google.com/7276, reset GPS data, then rebooted just for kicks, but my GPS refused to lock in Maps even after waiting 5 minutes. So I tried to launch some of the problem apps anyway, and they still force closed on me. For that matter, when launching them, the GPS icon in the notification bar never appeared.

So I switched back to www.spirent-lcs.com/7275, reset GPS data, and everything was back like it was before. GPS locks in quick, but reports wonky stats, and still getting FCs on various location aware apps.

BTW, thanks for the effort you've put into this so far! :)
[Captivate Android Development] mastergrillo:
I updated to 1.1 and im getting the same issue going to reflash see if it fixes it
[Captivate Android Development] watsa:
Dont, there is still some issue..
[Captivate Android Development] sepherian:
Will the JK4 modem work with this?

Sent from a phone controlling a computer controlling a different phone
[Captivate Android Development] watsa:
JK4 is an I9000 modem. This is an I897 based ROM.
[Captivate Android Development] killer_raj:
good job buddy....thanx here(as my thanx limit is over)

i just posted this on his apex thread today..

REQUEST to all the USERS of APEX ...

u guys get 5 thanx limit per day..pls dont waste it..use it everyday....thats a big appreciation for devs here...

as i see watsa has 2500 posts..but just 630 thanx...which is around 25% of his total posts..(coz he replies to all small small problem and instantly)....

and few other devs r having 50% ratio or more...

so pls press thanx...thats a big boost for devs and for those who likes to help

i was using xda classic all these while..so didnt hav thanx option...

by the way watsa..i could press thanx 8 times instead of 5...

and used all...

and now i m seein that he is gettin appreciation in form of thanx....i would like to see atleast 1000 thanx by one week....and its only possible with appreciation of users...

because he deserves it....

cheerssssssssss!!!!!

EDIT...now its abt time...to change my signature... ;)
[Captivate Android Development] RichMD:
What themes can we use without breaking any custom fixes? Would.PaulDiddy work? It says for jvr (i9000). Hopefully, sensation will be done soon.
[Captivate Android Development] :
Really noob question, but do metamorph themes work with this rom?
[Captivate Android Development] Exostenza:
Even though I am not running this as I am super happy with Apex 9.2 I would just like to thank you watsa for working on this ROM. When it has progressed to the point where it has all of the features that Apex packs I will switch over for sure.

Again, thank you!
[Captivate Android Development] watsa:
can u link me to it?
[Captivate Android Development] :
Fail.....I realized they have to be compatible with certain roms, and aren't universal.....
[Captivate Android Development] :
Refreshed page and saw Pinnacle 1.1.1 :eek: rolling out updates all day err'day lol
[Captivate Android Development] watsa:
This was needed. It was cauing various apps to FC. Was a stupid mistake from me :o
[Captivate Android Development] :
Stupid mistake, fixed in less than a day. This is why I loved Apex. Now I can have Apex (minus voodoo, kernel choices, etc; ) and audience chip support :D. Thanks!
[Captivate Android Development] syanz87:
Namaskar Watsa Ji Maharaj... getting great battery life on this Pinnacle rom..

i updated to v1.1.. again having that phone.apk FC problem... i had to replace that file again with apex jvr's........ except this not a single problem at all.. gps locks in 2-3 seconds even with 2 visible sats... GREAT WORK... Thanku....
[Captivate Android Development] Fate-Silver:
I wanna ask:

a.) If I have installed this ROM by using RFS File System, can I enable the LagFix again later on? Will it works?

b.) If I use a i9000 based Modem in this ROM, will I lose a bit of Call Quality?

Thanks.
[Captivate Android Development] Rrryan2:
This uses a stock RFS kernel. For the time being, RFS is all that's available until either source drops or someone figures out a hack for ext4 like DG did for KF1 (Cog5v2).

This is an I897 ROM/kernel. I9000 modems will not work.
[Captivate Android Development] nrgaway:
Are there any kernels that work with this rom that support bln?
[Captivate Android Development] watsa:
No there is only one kernel that works with KH3 ROMs
[Captivate Android Development] xpakage:
GPS

I installed the 1.1.1 update and I still get crazy GPS with GPS test and Copilot. Is something still wrong you are working on or should I reflash?
[Captivate Android Development] watsa:
:eek: try reflashing. I have 3 sats available all between 30-40 SNR :confused:
[Captivate Android Development] watsa:
Hey buddy you sure you are not restoring some data? Nobody else is having this problem :confused:
[Captivate Android Development] syanz87:
I also have the same result... But its fine... It gives me 10 meters accuracy with just 2 sats.....
[Captivate Android Development] syanz87:
No sir.. I didnt restore any data..previously i was on apex 9.2 jvr.. Firstly i flashed stock kh3 without BL, coz i was already on kf1 BL... Then flashed stock kh3 cwm kernel.. Done All wipings in cwm... Then flashed this pinnacle.....

Its ok now with jvrs phone.apk
[Captivate Android Development] xpakage:
Watsa- reflashed 1.1.1 from stock and it is fixed. Now back to 3 or 4 sats over 40 SNR so it is good :D
[Captivate Android Development] watsa:
Thanks buddy for confirming that. It is still strange that no matter how much I have messed up but GPS test shows SNR of 161 :eek:
[Captivate Android Development] Coldheat1906:
Help.....have Firmware Upgrade Fal!!! on screen

Okay, I really think that I messed up my phone trying to flash the bootloaders....

On my phone now I have a picture of:

A phone with a triangle and a computer on it.... and it says....

"Firmware upgrade Fail!!! Try Recovery mode!!!""

And it still does not work..... Any help will be much appreciated :confused::confused::confused::confused::confused::confused::confused:
[Captivate Android Development] mrhaley30705:
Pull the battery, restart computer. When you insert battery and attempt dl mode, it will go back to hardware failure screen. Don't freak out. Treat that screen as your download screen. Odin should recognize your phone and let you flash from there.
[Captivate Android Development] Coldheat1906:
Thanks that worked!! reflashing rom now.

Last time that I flashed the room (after following the instructions) I was in a boot loop. Hope this time works out better.

EDIT: Still not working. reflashed kernel and I am still in a boot loop.

Any suggestions?
[Captivate Android Development] RichMD:
Did you apply a theme by any chance? I also have no problems with the stock phone. You are all set with switching - just curious and it may save you a bit of trouble on updates.
[Captivate Android Development] RichMD:
Hi Watsa, I flashed the 1.1.1 update this morning and I still also saw one sat with ridiculous strength. I haven't seen any apps FC but obviously something isn't right. I will flash 1.1.1 from stock which will probably fix it for me too but do you want me to enable any logging, etc to capture what is happening before I reflash?

Also, does it make any sense to have a GPS lock with only one satellite? Unless it is using AGPS (land-based signals) as well, I can't see how one satellite could provide a lock.
[Captivate Android Development] RichMD:
You should uncheck "auto reboot" and flash the kernel. When it is done, disconnect and pull the battery. Reinsert the battery, hold vol up and down and power just until you see the AT&T screen and let go of all the buttons - that should put you in recovery mode. Do those exact steps not work for you?
[Captivate Android Development] mrhaley30705:
Flash the safe kf1 in my sig, then flash Pinnacle. Use the full Odin version, not the 1 click.
[Captivate Android Development] Roof King:
Weatherbug working after the update.

Thanks!
[Captivate Android Development] low99:
working now, guess perhaps it's because I didn't set tw4 as my default launcher before this. Thanks though.

this would be so totally awesome, because I get a carrier message after every call reporting the balance and it resets my notification volume, even the app quick setting which had the option to link call and notification volume didn't work, both ringer and notification got pulled back to the notification volume's default. 2 thumbs up :D
[Captivate Android Development] watsa:
yea let me know how it goes after a fresh flash
[Captivate Android Development] timn2bama:
working for me again to! thanks!
[Captivate Android Development] Coldheat1906:
Ok, I flashed safe KF1 in your sig and it worked now after the I flash the new Bootloaders and Kernel I can not get into Recovery mode using:

Vol UP + Vol Down + Power = Recovery
[Captivate Android Development] Krynn!:
Thanks! I installed the 1.1 -> 1.1.1 update and all of the FCs are now gone! :D

I was still showing some weirdness with the GPS though... Never saw more than 3 satellites and on one of them, the signal strength would be in excess of 100, sometimes over 200. I tried wiping data and playing with the SUPL settings again just to be sure, but was still seeing things going goofy. So I rebooted into recovery, and wiped cache, dalvik-cache, and just to be sure, did a factory reset. No luck there, I was still showing wonky GPS signal levels.

And that's the ticket. A fresh flash of 1.1.1 fixed it. My signal strengths are now showing sane numbers, and I'm seeing more than just 3 satellites.

So, to recap, the 1.1.1 update fixes the force closes, but if you want to fix the GPS signal strengths, you'll need to flash the full 1.1.1 package.

Thanks for the updates, Watsa!!!! :D
[Captivate Android Development] watsa:
Ok so I am pulling out non wipe update then. Thanks buddy
[Captivate Android Development] RichMD:
Have you tried installing ROM manager and the recovery and then choose reboot to recovery from that app? Do you have ADB installed on your computer - you could also use that to reboot to recovery.
[Captivate Android Development] Coldheat1906:
Will try that now
[Captivate Android Development] eep2378:
Recovery mode for GB is Volume up + Power, I believe.
[Captivate Android Development] watsa:
Thats only for I9000 BL
[Captivate Android Development] DanielGoff527:
Ran v1.1 for a day or so, data network seems to connect and disconnect at random when I have WiFi connected (as in, Wifi is on and connected, and the 3G symbol will randomly pop up for extended periods of time in the status bar and eventually go away), and I think it's killing my battery. Any ideas?
[Captivate Android Development] cnu4u:
I had problem of this key combo not working when coming from stock. after going back to stock, I had to go do software update from Settings --> update, to make this key combo work... Just check if that's the case for you....
[Captivate Android Development] syanz87:
I did nothing... No theme no mod....
[Captivate Android Development] watsa:
lol really? Mr 1 star come out and speak your mind
[Captivate Android Development] climber1872000:
Computer not recognizing device

Watsa,

First off, as usual, great ROM!

Okay, I have been running this KH3 build since your initial release a couple of days ago. All of a sudden this morning I plugged my phone into my computer to transfer some files over and out of nowhere I get the "One of the USB devices attached to this computer has malfunctioned, and windows does not recognize it". When I take a look at the details of the error I get "Windows has stopped this device because it has reported problems. (Code 43)". I have tried everything including 4 different computers. I have flashed back to Apex 9.2 and Dlev 4.2 in hopes that it would solve the issue, but no luck. I was going to flash back to stock but, obviously, Odin won't recognize my device either. I had my phone hooked up last night transferring over framework.apk to use in the UOT kitchen and it was working just fine. I have spent the past hour and a half searching threads for solutions but I cannot find any. At this point I am at a loss for any other ideas to solve this issue. :confused: Any help would be greatly appreciated.
[Captivate Android Development] watsa:
Have you tried:

1. rebooting both computer and phone

2. changing USB port

3. reinstalling drivers
[Captivate Android Development] Cdub5:
Wondering if this might be a Kh3 bug. I have the same problem, and I'm running Nuclear Fusion 2.3.4
[Captivate Android Development] DanielGoff527:
To quote His Dudeness, "this is a bummer man...that's a bummer"
[Captivate Android Development] oriveradel:
ok far no problems...and I left my phone fully charge before I went to bed... 10 hours later still at 97%... nice...and GPS is working very fast, of course I am using copilot, but you need to change the GPS settings...

this is how I do it it works like a charm

turn off Use Wireless Networks under setings > location and security

enter angry gps and change to:*#*#3214789650#*#*

Test mode: S/W Test

OP MODE: STANDALONE

Start Mode: HOT Start

GPS +: ON

GPS LOGGING: ON

Dynamic Accuracy: ON

Time OUT 255

Accuracy:50

SUPL SETTINGS:

Custom config

supl.google.com

7276

Secure Socket:OFF

SUPL mode: SUPL

back all the way out, reboot

turn on Use wireless Network settings>location and Security

enter back angry pgs, get phone access to the sky, and run tracking test, it should right away list satellites...and in my case after 10 seconds or so locks and gives my location info.

press back to go to previous screen and run TTFF test> start GPS and again it will show satellites and lock info including the time it took to lock ...get out your done!

test Google Navigation it should lock at same time it showed on TTFF test.. in my case 14 Secs Enjoy!

Thanks watsa... I tried all other H3 rom and nothing run as smooth as yours!
[Captivate Android Development] watsa:
lockscreen port begins :cool: much easier to add them in I9000 ROM as IDs are not messed up :(
[Captivate Android Development] FirstNoobToBrickHisPhone:
This is the most solid rom I ever flashed yet.

With the Samsung Adrenaline Shot v6 tweak, Tegrak OC, the awesome boog kernel. The apps where I used to have lag, where GO Launcher used to annoyingly restart by itself. No longer happens.

Thanks watsaa
[Captivate Android Development] climber1872000:
Yes sir. I've tried it all. Nothing works. I've even tried different cables.
[Captivate Android Development] oriveradel:
I had that problem long time ago, remove you external sd card, get your phone in download mod plug in let the computer detect and install drivers again.

remove battery intall sd card again, keep usb unplug, turn phone on, then format both cards, reboot plug on computer. that did it for me good luck!
[Captivate Android Development] climber1872000:
Unfortunately I don't have an external sd card installed. Thanks for the suggestion though
[Captivate Android Development] oriveradel:
one more helpful step for those flash addicts like me...

I don't need to wait for full battery charge to flash, I flash at any battery charge (as long as you have enough for flash a new rom), then use the battery calibration app, which gives 100% calibration, and when I unplug charger does n't go down to 90 -95, it stays at 100% !

flash your rom, install battery calibration, reboot. plug usb charger till 100%, unplug, turn phone off, plug till you get 100%. turn back on, plug again till you get 100%, run battery calibration which will show steps to do.. your done!

I found with these steps when I ungplug my charger 100% charge last for awhile, no longer goes down like many complaint of dropping right away to 90ish...
[Captivate Android Development] oriveradel:
you still can do it with your internal sd card.
[Captivate Android Development] climber1872000:
I'll give it a shot when I get home and report back.
[Captivate Android Development] ninjuh:
How come all apps are automatically installed to my external SD card?
[Captivate Android Development] Ruddy64:
I flushed this rom in the morning and so far so good. But i have one problem. I can't change lockscreen. No matter which lock i chose, it does not change. Do i need to re flash the rom or can i do something else? Thanx.
[Captivate Android Development] xTRUEx:
There are no extra lockscreens
[Captivate Android Development] Ruddy64:
When i go to settings-device custom.-lockscreen it gives me options for 5 or 6 different locks. EPIC, ROTARY, etc. You mean that they don't work? Why are they there then?
[Captivate Android Development] byrdtulsa:
Watsa said he was working on them now...just wait till next update
[Captivate Android Development] Rrryan2:
No init.d support in this kernel yet == no point in flashing the SAS tweaks.