yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note 3] kyogre504:
Problem with weather widgit and connecting to Gear on new update

Installed the new update(1/8/14) and the weather widgit would force close/not start. Also tried connecting my gear 1 with the gear manager and got the message saying "cannot connect because device is not supported"

Edit: The predictive text feature for the stock keyboard does not work. Overall, good rom and thank you for your work!
[T-Mobile Samsung Galaxy Note 3] Techngro:
If you're testing to see whether it works, I also got the OTA notice.
[T-Mobile Samsung Galaxy Note 3] MasterX007:
Still having problems
[T-Mobile Samsung Galaxy Note 3] tupirujp:
Why is these ROM on general ?
[T-Mobile Samsung Galaxy Note 3] tat2messiah:
why when i try to install new update it fails saying unable to open zip
[T-Mobile Samsung Galaxy Note 3] alek889:
Bad download...Try to download the zip file again.Install went smooth for me.
[T-Mobile Samsung Galaxy Note 3] fenixjn:
Any ideas on how to hide persistent notification items from the lockscreen, like Tasker? For some reason the ROM is handling these like they are actual notifications on the lockscreen rather than background processes. I will post a picture if needed. Also, the Poweramp controls' colors are displaying very weird on the notification drop down: the controls are a different tone of white but barely visible. I am aware this might be a problem on the application itself (the colors look fine in a dark themed ROM such as any pre-L ROMs).
[T-Mobile Samsung Galaxy Note 3] MasterX007:
Pictures would be great
[T-Mobile Samsung Galaxy Note 3] catchjeff:
GPS not working

Have 3 questions actually.

1 I cannot get the GPS to stick using GPS only to locate. It keeps searching and searching and not sticking.

2 When I flashed the newest update to v1 the phone rebooted itself into twrp recovery without me doing a thing. Is this something new? I have never had my N3 or any 9ther phone reboot itself into recovery after flashing a ROM. I first flashed the original tweak then v1 and now the update.

3 I noticed that on the Chrome app the address bar is different. The tab button that tells you how many tabs you have opened is gone alone with the option to refresh the page without having to hit the menu button on the phone. Is this new with lollipop or is it because the Lollipop leak is not official so things are whacky like that?

Thank you very much

jeff

---------- Post added at 09:51 AM ---------- Previous post was at 09:48 AM ----------

The notifications on the lock screen are a new Lollipop thing. Google is supposingly working on a fix for that. No way to turn that off. This is where xposed comes in handy.
[T-Mobile Samsung Galaxy Note 3] alek889:
1-??

2-??

3-Chrome tabs in lollipop are built-in the recents application(holding home button).If you like the "classic" way,go to chrome settings/Merge tabs and app and turn it off from there.
[T-Mobile Samsung Galaxy Note 3] bigdreco:
I posted the weather widget issue in the Q&A section for this rom.. I was told to do a clean install.. Because I did a dirty flash over the old version..

I'm not sure if it will fix the problem because I didn't want to go thru all the hassle.. I just deleted the widget off the home screen and I haven't had a FC since..
[T-Mobile Samsung Galaxy Note 3] fenixjn:
As requested:

This is how normally looks when unlocked: notice I am running a system monitor and tasker as background tasks

[IMG="Home Screen"]http://xdaforums.com/attachment.php?attachmentid=3108377&stc=1&d=1420914907[/IMG]

And this is how it looks when the lockscreen takes over:

[IMG="Locked"]http://xdaforums.com/attachment.php?attachmentid=3108378&stc=1&d=1420914907[/IMG]

(Sorry about the size, I don't see an option to resize when posting)

As you can see, those two are background tasks/processes and they cannot be dismissed like regular notifications.

And this is how PowerAmp looks:

See how the buttons are a shade of white that almost blends with the background?
[T-Mobile Samsung Galaxy Note 3] ajamils:
Been running the rom for couple of days and it's been really good with excellent battery life. The following are the only issue I've come across so far:

- Flashlight does not work. It force closes as soon as I open it.

- Battery themes do not work.

- IR remote does not work. I've been using the Smart Remote app for few months now but with this ROM when I press any button, nothing happens. App registers the button press but my device (TV, AVR) does not react to it. Which makes me believe that IR blaster is not working.

Scribbled on Note 3.
[T-Mobile Samsung Galaxy Note 3] Techngro:
Just FYI, I am using Tiny Flashlight from the Play Store, and the Samsung WatchOn app (IR remote) and both are working for me.
[T-Mobile Samsung Galaxy Note 3] TechGoon954:
Nice:thumbup:
[T-Mobile Samsung Galaxy Note 3] catchjeff:
Thank you very much. I do not like it because it is going to cause some unneeded wear and tear on my physical home button and we all know that with Samsung the less you have to press the hard buttons the better.
[T-Mobile Samsung Galaxy Note 3] MasterX007:
First day of school development for the ROM is still coming just trying to get flashlight in toggle as requested and more
[T-Mobile Samsung Galaxy Note 3] dmonger11b:
The camera not recording is not a problem with the rom. It's a flash problem mine works just fine.https://www.dropbox.com/s/wrwyxf1gaweoj3z/20150112_141942.mp4?dl=0
[T-Mobile Samsung Galaxy Note 3] MasterX007:
I don't know how but front and rear camera work for me fine taking pictures or recording I will give a preview of it in action
[T-Mobile Samsung Galaxy Note 3] alek889:
Mine indeed crash.You said is a "flash problem".....any fix for that???
[T-Mobile Samsung Galaxy Note 3] bigstunta101:
Does anyone here have a list of apps they successfully removed or know a debloat zip that removes a lot of these useless Samsung apps?
[T-Mobile Samsung Galaxy Note 3] rktdoc:
Its not just this ROM but across several other 5.0 as well.

Recording and video playback problems reported, and it seems to be a compatibilty issue with 4.3 causing it.
[T-Mobile Samsung Galaxy Note 3] Techngro:
I don't know when this issue started, but I am having serious issues with the Samsung keyboard. It doesn't show you any auto-correct, and it doesn't do any of the stuff it normally does, like auto capitalize, etc. I had to install and switch to Google Keyboard. But I prefer the Samsung one because it stores my data.
[T-Mobile Samsung Galaxy Note 3] rktdoc:
I had the same problem, autospell mispelling words, very irritating.

Had to do a clean flash to fix, but noticed it also boots up faster after being powered down, and seems a little smoother overall.

Would be 100% ROM if would video record.
[T-Mobile Samsung Galaxy Note 3] alek889:
Do you have a N900w8 or N900t???
[T-Mobile Samsung Galaxy Note 3] rktdoc:
N900t.
[T-Mobile Samsung Galaxy Note 3] erikbacon:
I just noticed today that recording does not work for me too.

N900w8
[T-Mobile Samsung Galaxy Note 3] catchjeff:
I cannot get Microsoft Office Mobile running on this ROM. I keep getting force closing ad soon as I hit the app button. I have my Microsoft account app installed and signed in.

Microsoft Office works well on me nexus 7 2012 edition fine.
[T-Mobile Samsung Galaxy Note 3] Techngro:
I was on another ROM for a couple of weeks, and was gonna do a restore of Tweak, but decided to do a clean install instead. Fixed the Samsung keyboard issue like you said. Thanks.
[Moto G Q&A, Help & Troubleshooting] EternalFame:
Hey guys.

Today I wanted to downgrade my MG from 4.4.4 using a batch file with 4.4.2 files using fastboot.

Everything except gpt.bin and motoboot said Okay. These 2 failed :/

It didn't boot so I tried to flash TWRP and install a custom rom but every recovery says

E: cant mount system

E: cant mount data

E: cant mount cache

E: cant mount sdcard

In short, nothing mounts

When booting it up nothing more than the motorola logo shows up!

Did I **** up?
[Moto G Q&A, Help & Troubleshooting] Cheddart:
Yeah, u soft bricked your phone,but you van try wiping all partitions and flashing the stock ROM using the adb.
[Fire TV Q&A, Help & Troubleshooting] superfly611:
I've been looking for an actual guide or directions on how to update your Amazon fire TV from Gotham to kodi. I don't know if it's just an easy step or if there's something involved. Can someone help me on how to actually update XBMC to kodi. It would be greatly appreciated and I'm sure others would like it to.
[Fire TV Q&A, Help & Troubleshooting] amendolaro1:
Just install the Kodi apk. It will migrate your info from gotham over
[X 2014 Q&A, Help & Troubleshooting] goblue13579:
Edit: 20 character code, this is not a good idea.
[Samsung Galaxy Grand Quattro] maxpayne-x:
Hi everyone ,

My phone is Galaxy Grand Quattro GT-I8552 and

PDA: I8552XXANF2

CSC: I8552OJVANF1

MODEM: I8552XXANE1

I use stock rom and I has latest update. ( 15.06.2014).I read all root topics.But They are old topic.My phone has new updates.So

How to root my phone . Some new update owners have problems.Ex; Not root ,not cwm .

Do you have new idea or a way for new uptades phones.

[IMG="Update number"]http://i.imgur.com/7vT7ykL.png[/IMG]

​

​
[Samsung Galaxy Grand Quattro] maxpayne-x:
Is there an idea for this ?
[Optimus One, P500 Android Development] ibub:
To my brothers (you know who you are)

Long, long ago...

A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...

STATUS: NOT BOOTING

JENKINS SHUT DOWN

NO DOWNLOADS

The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.

I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.

Website:

http://androidarmv6.github.io/

Source code:

https://github.com/androidarmv6

You can watch development as it progresses, or you can sign in and participate here:

http://review.androidarmv6.org/#/q/status:merged

STATUS: NOT BOOTING

JENKINS SHUT DOWN

NO DOWNLOADS

sent from my towelrooted LG L34C using daishi4u bumped twrp 2.8.3.0 and bumped key-boot-recovery kernel
[Optimus One, P500 Android Development] ibub:
...as he looked back on the sleeping giants, exhausted from their long journey, the wizard Androidmeda new that he had taught them all that he could, and they had all that they needed. But he also knew that they would never be able to survive crossing the mountains into the new land. Only their child would be able...

Well I guess this is it my brothers. Seems that all has been tried, and CM-12 will not be released for armv6 devices. But many thanks to our devs for trying. It's been a long run. Amazing, just amazing.
[Optimus One, P500 Android Development] xu3sno:
Congrats! Nice preface wording, bro! :good: :cool:
[Optimus One, P500 Android Development] Dovidhalevi:
Great! and thanks.

I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.

I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.

How to proceed?

BTW: Link points to end-user builds (cm-11). We'll get there.
[Optimus One, P500 Android Development] ibub:
Thanks, link updated to View/All.

:)
[Optimus One, P500 Android Development] aayushARM:
This is great [MENTION=4912093]ibub[/MENTION] !

Thanks for taking the initiative of building CM12 for this device, which never seems to grow old..... ;)

The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated! :)

Waiting for it to boot for now... :D
[Optimus One, P500 Android Development] ibub:
Just to be clear, this is not my work. Androidarmv6 team (mainly androidmeda for p500) compiles these ROMs. Thanks belong to them (him). :)
[Optimus One, P500 Android Development] Casserole:
Wut? ART isn't compatible with ARMv6, AFAIK.
[Optimus One, P500 Android Development] ibub:
We shall soon see. ;)
[Optimus One, P500 Android Development] xu3sno:
CyanogenMod announces official CM12 Nightlies!

http://phandroid.com/2015/01/05/cyanogenmod-cm12-nightlies/

Do not even expect P500 on the list! :D

EDIT:

CyanogenMod 12 nightlies now available for 31 devices, based on Android 5.0.1 Lollipop (LRX22C). LG Optimus One is out of the list to be sure :)

http://blog.gsmarena.com/cyanogenmo...able-31-devices-based-android-5-0-1-lollipop/

While in other hand, our devs are working to port experimentally newer version of CM12 (Android 5.0.2 LRX22G) on armv6 obsolete devices, though! :good: :cool:
[Optimus One, P500 Android Development] ibub:
You can look at development of android_art as it progresses here:

http://review.androidarmv6.org/#/q/status:merged

and here:

http://review.androidarmv6.org/#/c/7676/

;)
[Optimus One, P500 Android Development] xu3sno:
Who dares (try this on p500) win!

http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/

http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
[Optimus One, P500 Android Development] CCXAlex:
Trimmed>>Flashed>>Stuck at CM bootlogo :(
[Optimus One, P500 Android Development] xu3sno:
+1K :(

GERRIT_CHANGES: 7676 7748 7693 7651 7751 7792

7676: * runtime : make entrypoints ARM; if the target arch is lower than
armv7, set armv6.
* compiler: add a new define: ARM_MODE_WORKAROUND, enable it if
the target cpu is arm11. Use ARM assembler and replace
Thumb{1-2} opcodes with ARM ones. Update some code to
support new opcodes

NOTE: kArm is not implemented, probably it use to work only in
portable mode.
7748: Compatibility work around for bad graphics driver dependency
7693: legacy OMX: squashed commit for legacy OMX support for LP
7651: Revert "Revert "Turn on BLE, GATT, and SMP of Bluetooth stack""
7751: msm7x27-common: Initial cm-12 bringup
7792: jemalloc: Force gcc for atomic functions
GCC built-in functions provide advanced things like prefetch, expected, synchronization...

Bootloog attached.

It seems bootloop's culprit is regarding with dynamic shared libraries (lib*.so) which must be fixed first.
[Optimus One, P500 Android Development] Any PlayStore:
It does not work on any device arvm6.

Link
[Optimus One, P500 Android Development] xu3sno:
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)

Androidmeda built it for testing via Jenkins, if you dare to waste your time! :)

http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/

ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
[Optimus One, P500 Android Development] Any PlayStore:
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.

Thanks for the update by [MENTION=4685929]xu3sno[/MENTION]
[Optimus One, P500 Android Development] xu3sno:
[MENTION=6082581]Any PlayStore[/MENTION]

also [MENTION=5470389]CCXAlex[/MENTION] (may be you have luck to try it, but I doubt :))

Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500. :D

Trimmed > clean installed > rebooted > boot loop :( As previous attempt, it seems lib*.so need to be fixed (?)

Don't know it's wasting my time or not :)
[Optimus One, P500 Android Development] Dovidhalevi:
Yes, yes, we know or should know. But, hey, who does not want to be the first to see this play? The only reason I am staying off is because of the CM tricks with switching system and data partitions meaning recoveries are not compatible.

Anyway, diehards within the CM universe, once in that bootloop if ART had indeed done its thing, check remaining system space and contents of those /system/app/... folders. My (un-) educated guess is that this may become the big problem.
[Optimus One, P500 Android Development] ibub:
I also attempted to install this. Initially my trimming method seems to have broken update binary, so flash failed. Next installed full ROM (/system =189MB) using [MENTION=4974969]HardLight[/MENTION] twrp 2.7.0.0 TLS (successfully flashed). Stuck at boot animation. No log (flashing while driving). ;)
[Optimus One, P500 Android Development] xu3sno:
Checked free space left on /system partition is ca. 21 MB of 200 MB total size. Contents of /system/app almost the same as in cm-11. It consist of apollo, browser, bluethoot, calendar,camera, gallery, .........WAPPushManager. While /system/app itself occupies 20.42 MB.
[Optimus One, P500 Android Development] xu3sno:
OT

Hey, (texting) flashing while driving is against the KY law, isn't it? :D

Drive safely bro! :)

End of OT
[Optimus One, P500 Android Development] Dovidhalevi:
Did ART do anything (i.e. "Android is upgrading ##/## ...") ??

Missing my point.

In CM-11, was /system/app/Apollo.apk (BTW, make this a user app!! Also Camera, Gallery, Calendar--install from Play)

In CM-12, is /system/app/Apollo/Apollo.apk , OK

If ART did anything (apparently big IF), what else is there? If Apollo.dex or equivalent gets placed there, well, we know the score! If ART did not do anything, obviously nothing is going to run.
[Optimus One, P500 Android Development] ibub:
Hey, how did you get screenshots? You got it to boot? Guess I'll try again. :)
[Optimus One, P500 Android Development] Dovidhalevi:
Look again. Those are from a file manager reading the ROM zip.
[Optimus One, P500 Android Development] Any PlayStore:
Do not waste your time. We will know, if the rom works on ARMv6. :D

http://s10.postimg.org/75g0d3ys9/Untitled.png

-----------

Need "@Notonlyeyes' help. You can give me a "bootanimation_AndroidL" for Galaxy Mini S5360. Many thanks
[Optimus One, P500 Android Development] Notonlyeyes:
OT

OT

Resolution?

view: http://xdaforums.com/showpost.php?p=53793211&postcount=290
[Optimus One, P500 Android Development] Any PlayStore:
240x320 Thanks noe
[Optimus One, P500 Android Development] Notonlyeyes:
OT

Bootanimation AndroidL for 240x320 ...by noe
[Optimus One, P500 Android Development] Any PlayStore:
I wonder why you add size 800x1280?
[Optimus One, P500 Android Development] Notonlyeyes:
for [MENTION=4685929]xu3sno[/MENTION] ...by noe
[Optimus One, P500 Android Development] xu3sno:
OT

Thanks noe. It works out of the box on my rooted Samsung Galaxy Tab 3 8" T311, cm11 (4.4.4)-20150112 :cool:

bye ....noe

End of OT
[Optimus One, P500 Android Development] xu3sno:
Build cm_p500-userdebug-cm-12.0 (Jan 15, 2015 9:33:54 PM)

http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1315/

EDIT

Failed!. At least no need for wasting the bandwidth and time! :)
[Optimus One, P500 Android Development] xu3sno:
Okay, now you could give a try this experimental: Build cm_p500-userdebug-cm-12.0 (Jan 16, 2015 4:39:15 PM)

As usual, it's built by our dev androidmeda

Who knows, you have luck system booted and you didn't waste your weekend and bandwidth and bring a good news for us! :D

Go here: http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1319/

and download the rom (size:161.66 MB, previous build 20150111 just 118.73 MB ) : http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150116-EXPERIMENTAL-p500.zip

GERRIT_CHANGES	: 7676 7748 7693 7792 7799
[Optimus One, P500 Android Development] ibub:
Zip is huge(162MB) uncompressed. /system =381MB. This will take serious trimming.
[Optimus One, P500 Android Development] Notonlyeyes:
this version test os2sd f2fs, recovery twrp multi...by noe
[Optimus One, P500 Android Development] xu3sno:
Yeah, I think you're right. :)

ROM (odex, therefore has a huge size of 161.66 MB > extracted to 385.68 MB > trimmed to 349.13 MB > zipped to 150.60 MB. No chance to flash it into internal memory. Must be installed into sdcard (OS2SD) by using [MENTION=4974969]HardLight[/MENTION] TWRP 2.8.3.0 multi as [MENTION=4553005]Notonlyeyes[/MENTION] said.! I have no chance to use it, need new sdcard and formatted to f2fs. :(

Waiting for someone to test it :) [MENTION=5470389]CCXAlex[/MENTION] , [MENTION=6082581]Any PlayStore[/MENTION]
[Optimus One, P500 Android Development] xu3sno:
I did it, but still got 150 MB. Can't delete .odex files, otherwise it failed to flash/reboot system (?).
[Optimus One, P500 Android Development] xu3sno:
Insisted flash trimmed (150 MB) experimental build 20150116 to internal memory, and (of course) ended up to recovery failed! :)
[Optimus One, P500 Android Development] ibub:
I opened all of the apks in /system/app and /system/priv-app. None of them have classes.dex, so deleting odex files would definitely be a bad idea. I guess we need to go with os2sd. I think I can afford a new SD.

;)
[Optimus One, P500 Android Development] xu3sno:
In progress: Build cm_p500-userdebug-cm-12.0 (Jan 17, 2015 1:38:33 PM)

Started by user androidmeda

As of posting, build has been executing for 5 min 27 sec.

http://jenkins.androidarmv6.org/job/cm-experimental/1325/

EDIT:

It failed! Just took 6 min 27 sec only!
[Optimus One, P500 Android Development] Dovidhalevi:
Yep, looks like a job for o2sd.

How big is the total of /system/app? Alternative might be to place this elsewhere and symlink.
[Optimus One, P500 Android Development] xu3sno:
Last successful Build cm_p500-eng-cm-12.0 (Jan 17, 2015 6:52:02 PM)

http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1326/

As usual it started by user androidmeda

ROM: Size: 162.76 MB, http://jenkins.androidarmv6.org/vie...cm-12-20150117-EXPERIMENTAL-twrp2840-p500.zip

Required recovery TWRP 2.8.4.0 (?) [MENTION=4974969]HardLight[/MENTION], could you please develop it for OS2SD-multi? Sorry to disturb your weekend :(. Thanks. Recovery image: http://jenkins.androidarmv6.org/vie...perimental/1326/artifact/archive/recovery.img

[MENTION=4708203]Dovidhalevi[/MENTION]

On 20150116 /system/app size is about 30 MB, I have trimmed to 19 MB.
[Optimus One, P500 Android Development] HardLight:
CM12 will be OS2SD

It is experimental recovery build made for cm12. As you see I committed OS2SD patches to androidarmv6 so upcoming cm12 development for p500 probably will be using external sd for keeping /data and /system, because android 5.0.x is noticeably larger than kitkat.

This recovery is just for OS2SD so if you want have multi version just use TWRP multi 2.8.3.0 from my cm11 thread, it will work.

Also sd preparation is same as for cm11 os2sd:

Use TWRP-2.7.3.0-MULTI (in OS2SD mode) partitioner tool: Advanced>Partition SD Card

OS2SD System 512 (or more)

Swap Size 128 (or more)

OS2SD Data 1024 (or more)

Go to Wipe>Advanced Wipe select Data. Then Repair or Change File System>Change File System>F2FS