• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][ICS] Paranoid Android Ver1.6 Beta from source (31JUL2013)

I'm getting a weird, issue, not sure if it is just my phone, bad battery, or something rom related, my phone keeps getting a black screen I can see that the lights are on but the screen has gone black, I can't get out of this till I pull the battery and reboot, I have tried fixing permissions, and swapping batteries, happened with both, I am running the 9/6 tester

just tried to make a backup so I could try jumping to old rom it comes up with "can't mount /hidden"

edit: well the phone finally died, wouldn't let me install the stock rom, so I went and got the lg F3 at walmart, it was on sale for 149.99, I would like to say thanx to all the devs that made this phone usable for so long
 
Hi Folks! I just wanted to pop in this thread to say goodbye: I bought a Samsung Galaxy Ring from Walmart today. I don't know how good the Ring is supposed to be, but it comes with Jellybean and was on sale for $129, so I bought it. I've only played with it for an hour or so, but so far it's ridiculously better than the Triumph: it's got Jellybean, the GPS locks in like... 3 seconds, and Wi-Fi comes on in 2-3 seconds. It's amazing!

But I do want to thank BSydz, Whyzor, Tickerguy, g60madman,isaacj87, mantera, adamto, Chairshot215, dsmryder, b_randon14, yumbrad and any others I might have left out for all their hard work on the Triumph. You guys made a dodgy phone much, much better, and for that I thank you!

Happy trails, folks!
 
The Sept. 6 build is much improved. Touchscreen is way better and it seems to have taken care of most of the problems I was having. Battery life does seem to be worse, but it's an easy trade-off. I haven't had any reboots, no jumbled text.
 
By using the current tester as well as the cm9 GPU kernel, which i think is the one we referred to as the "gaming kernel", I've been able to play the massive games "yesterday" and "the room" all the way through without any real interruptions. I consider that quite a triumph for the triumph, a "legacy device". I intend to stick with this device till the bitter end, and would be happy to assist with any testing of this rom or any cm 10 / jelly bean roms currently in development. Live in the city, so I don't drive and cannot comment on the GPS. The number of bugs that I see in this ROM is roughly equivalent to what I would expect that of most stock phones. I've spent so much time in recovery, flashing different roms kernels ,Google now, & a variety of G apps , but I feel quite at home there, and I'd love to contribute in any way that I can. So keep me in mind for any upcoming Frankenstein projects you may need , and thank you again for all of your brilliance ;I can hardly remember what Froyo looks like.
 
jerrspud said:
I'll take dodgy over Korean any day
Click to expand...

Ouch! Isn't our phone Chinese? I used to love my OV because it was made in a free state. Our phone is a HUAWEI! My TouchPal keyboard even recognized and capitalised HUAWEI! See? HUAWEI HUAWEI HUAWEI! Soon, they'll be making our toothpaste, and then...
 
BSydz said:
Here's the new tester, fixed touch screen, flashlight toggle, proximity sensor, and hopefully the roaming issue, along with other stability issues. See previuos post for a few details.


pa_triumph-1.6a-06SEP2013-132655.zip

Let me know how it goes.
Click to expand...

I did a backup, format cache and flashed this. This build runs so much smoother @1.4GHz than the July 31 build, which was still lagging at 1.4GHz

Wifi connectivity detection seems to be not working (turn blue with Internet connectivity), same problem with mobile data

GPS, it locks faster but in Google Maps it keeps showing that I am off the road and trying to reroute. Error 60ft+, which wasn't a problem in the July 31 release
Google Maps may still lags a few seconds behind at the beginning of navigation (not sure if this is related to accuracy/error), but no more freezes.


Tether, it works. But still with tether on, the phone itself has no internet connectivity, if you make a phone call with tether on, wifi tether is automatically disabled and the phone loses Internet connection until reboot (CDMA field test says Data Connection physical link down), tried toggle airplane mode or mobile data, didn't work
 
intransit74 said:
Ouch! Isn't our phone Chinese? I used to love my OV because it was made in a free state. Our phone is a HUAWEI! My TouchPal keyboard even recognized and capitalised HUAWEI! See? HUAWEI HUAWEI HUAWEI! Soon, they'll be making our toothpaste, and then...
Click to expand...
Yes.. Made by Foxcomm
 
It seems like there are quite a few people who don't care all that much about getting video recording working with this ROM, which is kind of a bummer. Video recording is probably the one feature I've been crossing my fingers the most for... I'd say I shoot short video clips way more often than taking pictures (at least, I used to). I love having CM9 on my Triumph and this ROM has gotten better & better with every release... I'm running the 09/06 tester and so far I haven't had any of the lag/lock-up problems I was experiencing before and it's much smoother in general. So, kudos to you Mr. Dev. And thank you :)

I'm still going to keep my fingers crossed for video! I don't know what I'd do if I were to check this thread one day and see that video recording on a CM9 Triumph is fully functional. :p
 
realdreams said:
You mean Foxconn? LOL
Click to expand...

Back to the phone, I've heard that 245 minimum uses the same energy as 61 on set CPU. Has anyone found, in their opinion, a perfect, or at least competent CPU setting, governor and scheduler use on the new build? Particularly for daytime dormancy and high end gaming? I'm wondering just how fast a setting is TOO fast, and if some force closes are due to overclocking (perhaps increasing memory use? ) I'm sure there's a better way to free up our low RAM than freezing most of my apps before playing a large game. I'd love to hear your feedback.
 
intransit74 said:
The maker of our phone has installed suicide netting around their mega-city in mainland China. Sucks to think that the 16 year-old "intern" that put the final touches in my MT quietly got up, walked across the room, and took a swan dive six stories into some unforgiving plastic mesh, then silently returned to her work station, looking like she'd just stepped out for a Spiderman tattoo on her face.
Back to the phone, I've heard that 245 minimum uses the same energy as 61 on set CPU. Has anyone found, in their opinion, a perfect, or at least competent CPU setting, governor and scheduler use on the new build? Particularly for daytime dormancy and high end gaming? I'm wondering just how fast a setting is TOO fast, and if some force closes are due to overclocking (perhaps increasing memory use? ) I'm sure there's a better way to free up our low RAM than freezing most of my apps before playing a large game. I'd love to hear your feedback!
Click to expand...


In my testing I found that the lower clock speed does make a difference. It's small after ~500MHz, but does make a difference. I would run my MT at ~24MHz with an overclock of 1.4GHz. It worked very well for me with the interactive governer.

I also stayed on GB because if the low level of RAM for our phone. That at the camera worked at the time.
 
intransit74 said:
The maker of our phone has installed suicide netting around their mega-city in mainland China. Sucks to think that the 16 year-old "intern" that put the final touches in my MT quietly got up, walked across the room, and took a swan dive six stories into some unforgiving plastic mesh, then silently returned to her work station, looking like she'd just stepped out for a Spiderman tattoo on her face.
Back to the phone, I've heard that 245 minimum uses the same energy as 61 on set CPU. Has anyone found, in their opinion, a perfect, or at least competent CPU setting, governor and scheduler use on the new build? Particularly for daytime dormancy and high end gaming? I'm wondering just how fast a setting is TOO fast, and if some force closes are due to overclocking (perhaps increasing memory use? ) I'm sure there's a better way to free up our low RAM than freezing most of my apps before playing a large game. I'd love to hear your feedback!
Click to expand...

Sounds like Foxconn is the only place suicide happens... If you look at ratio, Foxconn isn't that bad....
 
dsmryder said:
In my testing I found that the lower clock speed does make a difference. It's small after ~500MHz, but does make a difference. I would run my MT at ~24MHz with an overclock of 1.4GHz. It worked very well for me with the interactive governer.

I also stayed on GB because if the low level of RAM for our phone. That at the camera worked at the time.
Click to expand...

That's the tough trade-off for me. I'm curious if some of the newer, larger games would play on CM7, but getting all that memory back is seriously tempting. I was thinking of flashing it again just yesterday; doing a sort of pro/con list in my head. I still keep it on my card. (^_-)-☆
 
jerrspud said:
I just ignored that comment... it had nothing to do with my problem with Samsung.
Click to expand...
b ".


I now see the error in my perception. You seem to have substituted the word "Samsung" with the word "Korean". I erroneously heeded the text rather than the intent. Please forgive the faux pas, on behalf of koreans everywhere and pay no heed to my further factoids.

Now, back to the phone. I think I may try to run larger games on CM7, in hopes of gaining precious memory. I've grown so long ago accustomed to ROM switching that it won't even an inconvenience to try.
 
8 days with no activity... How long until this thread is officially declared dead...? :'(

Anyway, in the last couple weeks I have been having a lot of issues with sending text messages. I will have good network coverage (2 or more bars) but still get the little red triangle with the exclamation point in it, as well as the notification in my status bar. It doesn't seem to matter if I'm connected to Wi-Fi or not either. Usually messages will send on the second try but occasionally it will take three, four, or sometimes even more tries before they go through.

Does anyone know if this is a network issue with VM/Sprint or is this a possible bug creeping up with the ROM? For the record, I'm still running the 31JUL2013 build, and I haven't added or updated any apps since I installed the ROM a couple months ago.
 
GKNByNW said:
8 days with no activity... How long until this thread is officially declared dead...? :'(

Anyway, in the last couple weeks I have been having a lot of issues with sending text messages. I will have good network coverage (2 or more bars) but still get the little red triangle with the exclamation point in it, as well as the notification in my status bar. It doesn't seem to matter if I'm connected to Wi-Fi or not either. Usually messages will send on the second try but occasionally it will take three, four, or sometimes even more tries before they go through.

Does anyone know if this is a network issue with VM/Sprint or is this a possible bug creeping up with the ROM? For the record, I'm still running the 31JUL2013 build, and I haven't added or updated any apps since I installed the ROM a couple months ago.
Click to expand...

Could be something you installed or a setting you changed, bugs don't 'creep up' they either exist, or they arise from other changes you apply
 
SwoRNLeaDejZ said:
Could be something you installed or a setting you changed, bugs don't 'creep up' they either exist, or they arise from other changes you apply
Click to expand...

I should have clarified in my post that I have not only not added or even updated any apps, but I have also not changed any settings.
 
GKNByNW said:
8 days with no activity... How long until this thread is officially declared dead...? :'(

Anyway, in the last couple weeks I have been having a lot of issues with sending text messages. I will have good network coverage (2 or more bars) but still get the little red triangle with the exclamation point in it, as well as the notification in my status bar. It doesn't seem to matter if I'm connected to Wi-Fi or not either. Usually messages will send on the second try but occasionally it will take three, four, or sometimes even more tries before they go through.

Does anyone know if this is a network issue with VM/Sprint or is this a possible bug creeping up with the ROM? For the record, I'm still running the 31JUL2013 build, and I haven't added or updated any apps since I installed the ROM a couple months ago.
Click to expand...

When Sprint was upgrading the towers in my area I would send a text and it would come back as not sent, even though it was.
 
For some reason Google Play Store is not working in the Sep build (I upgraded from July 31 build without reflashing Gappas). The store always says no connection.
 
realdreams said:
For some reason Google Play Store is not working in the Sep build (I upgraded from July 31 build without reflashing Gappas). The store always says no connection.
Click to expand...

When you flash gapps it does more than just install apps. It has some shared libraries and scripts and links.
 
You must log in or register to reply here.
Back
Top Bottom